Eliminating the "duplicate state" variable Thread.started creates the scenario in which an OOM from the VM thrown out by Thread.start followed by invoking start a second time can result in duplicate Thread references being present in ThreadGroup (e.g. making ThreadGroup.activeCount return a too-high value).
- relates to
-
JDK-6988618 JCK test setDaemon0101 hangs on specific machine
- Resolved
-
JDK-7013961 Threads attached via JNI attach prevent daemon ThreadGroups from being destroyed
- Closed
-
JDK-6378434 (thread) IllegalThreadStateException invoking Thread.start after getting OOME (jdk5.0)
- Closed