Review Request (S) 8013945: CMS fatal error: must own lock MemberNameTable_lock
Staffan Larsen
staffan.larsen at oracle.com
Fri May 24 03:22:46 PDT 2013
Looks good!
/Staffan
On 24 maj 2013, at 11:29, serguei.spitsyn at oracle.com wrote:
> Please, review the fix for:
> bug: http://bugs.sun.com/view_bug.do?bug_id=8013945
> jbs: https://jbs.oracle.com/bugs/browse/JDK-8013945
>
> Open webrev:
> http://cr.openjdk.java.net/~sspitsyn/webrevs/2013/hotspot/8013945-JVMTI-JSR292.1/
>
> Summary:
> CMS calls InstanceKlass::release_C_heap_structures() concurrently.
> The "delete mnt" needs to take MemberNameTable_lock if !SafepointSynchronize::is_at_safepoint().
>
> Testing:
> The vm/mlvm and Nashorn tests, the tests listed in the bug report
>
> Thanks,
> Serguei
More information about the serviceability-dev
mailing list