JDK-4669456 : CompilerThread should not be a Java thread
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.1
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2002-04-16
  • Updated: 2002-07-17
  • Resolved: 2002-07-17
Related Reports
Relates :  
JDK-4666992 - b08: Permissions/threadGroupStopTest crash VM
Relates :  
JDK-4529296 - issuspended002 times out waiting for a bkpt with -Xcomp
Relates :  
JDK-4656449 - VM crashes on shutdown
Description
The CompilerThreads in HotSpot should not be Java threads. They end up in the
user-visible thread list in the main thread group and can therefore be operated
upon by Java code. This causes bad interactions with debuggers and operations
like Thread.stop(). It's likely that they were made Java threads in order to be
able to transition their state to _thread_in_native; they don't run any Java
bytecodes (or at least definitely should not.) We should make these threads non-
Java threads and fix any runtime assertions that come up in 1.4.2.
Comments
EVALUATION ###@###.### 2002-07-17 The concern about system threads, including the CompilerThread being externally visible was fixed via 4529296 and 4668611.
17-07-2002