Question regarding JVM crashes in GC
stefan.johansson at oracle.com
Mon Apr 10 12:31:49 UTC 2017
On 2017-04-06 17:51, Michael Rasmussen wrote:
> On 6 April 2017 at 18:36, Michael Rasmussen
> <michael.rasmussen at zeroturnaround.com> wrote:
>> I'm still trying to debug if it's somewhere in our native code that
>> triggers this, although I don't understand how/if we can touch
>> something this deep in the GC.
> Ok, think I've found the likely culprit. I think some of the
> instrumentation we're doing to these early classes are causing the
> Reference class to be loaded too soon!
> Would that explain this behavior?
I'm not sure I follow what too soon mean. For the GC we should be fine
as long as the offsets are correct, and you seem to have verified this.
I guess there could be an issue where loading the Reference class
earlier than expected could cause us to write bad oops into the
reference fields somehow and that would then crash in the GC. But I
would have expected that to have been caught by running with
More information about the hotspot-dev