RFR: 8340313: Crash due to invalid oop in nmethod after C1 patching
Thomas Schatzl
tschatzl at openjdk.org
Tue Oct 15 08:11:20 UTC 2024
On Fri, 11 Oct 2024 19:57:25 GMT, Dean Long <dlong at openjdk.org> wrote:
> @tschatzl , when we call register_nmethod(), do we really need to scan the oops immediately, or could that be delayed until the next safepoint?
Could be delayed at least for the STW collectors, but we want to avoid doing any work during gc as much as possible. This may be more tricky with concurrent gcs.
After some talk with @TobiHartmann we think that it is best and safer to extend the lock scope.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/21389#issuecomment-2413184441
More information about the hotspot-compiler-dev
mailing list