The JVMTI changes added a call to
JvmtiExport::post_compiled_method_unload_at_safepoint
to nmethod::flush. This means that the methodOop embedded in an nmethod
is live until the nmethod is flushed, not just until the the nmethod is
made a zombie. If a gc happens while the nmethod is a zombie, the
call to post_compiled_method_unload_at_safepoint can segv on the bad
methodOop.
JvmtiExport::post_compiled_method_unload_at_safepoint
to nmethod::flush. This means that the methodOop embedded in an nmethod
is live until the nmethod is flushed, not just until the the nmethod is
made a zombie. If a gc happens while the nmethod is a zombie, the
call to post_compiled_method_unload_at_safepoint can segv on the bad
methodOop.
- duplicates
-
JDK-4948473 nsk/jvmti/CompiledMethodUnload/compmethunload001 fails with segv
-
- Closed
-