-
Bug
-
Resolution: Fixed
-
P3
-
hs25, 7u60
-
b31
-
b35
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8016380 | 8 | Serguei Spitsyn | P3 | Resolved | Fixed | b94 |
JDK-8034017 | 7u80 | Serguei Spitsyn | P3 | Resolved | Fixed | b01 |
JDK-8060836 | 7u79 | Serguei Spitsyn | P3 | Resolved | Fixed | b01 |
JDK-8057270 | 7u76 | Serguei Spitsyn | P3 | Resolved | Fixed | b01 |
JDK-8035851 | 7u65 | Serguei Spitsyn | P3 | Resolved | Fixed | b01 |
JDK-8035457 | 7u60 | Serguei Spitsyn | P3 | Closed | Fixed | b08 |
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (C:\jprt\T\P1\151437.amurillo\s\src\share\vm\runtime\mutexLocker.cpp:150), pid=4800, tid=8288
# fatal error: must own lock MemberNameTable_lock
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b87) (build 1.8.0-ea-fastdebug-b87)
# Java VM: Java HotSpot(TM) Client VM (25.0-b31-internal-201305031514.amurillo.hs25-b31-snapshot-fastdebug compiled mode, sharing windows-x86 )
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
- backported by
-
JDK-8016380 CMS fatal error: must own lock MemberNameTable_lock
- Resolved
-
JDK-8034017 CMS fatal error: must own lock MemberNameTable_lock
- Resolved
-
JDK-8035851 CMS fatal error: must own lock MemberNameTable_lock
- Resolved
-
JDK-8057270 CMS fatal error: must own lock MemberNameTable_lock
- Resolved
-
JDK-8060836 CMS fatal error: must own lock MemberNameTable_lock
- Resolved
-
JDK-8035457 CMS fatal error: must own lock MemberNameTable_lock
- Closed
- relates to
-
JDK-8008511 JSR 292: MemberName vmtarget refs to methods must be updated at class redefinition
- Resolved
-
JDK-8011803 release_C_heap_structures is never called for anonymous classes.
- Closed