JDK-8344921 : jdk/internal/loader/ClassLoaderValue/ClassLoaderValueTest fails due to a JVM crash
  • Type: Bug
  • Component: core-libs
  • Affected Version: 19
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: os_x
  • CPU: aarch64
  • Submitted: 2024-11-25
  • Updated: 2025-11-04
  • Resolved: 2025-11-04
Related Reports
Relates :  
JDK-8345147 - Crash in libsystem_malloc.dylib`nanov2_malloc_type (ESR_EC_DABORT_EL0)
Description
The jdk/internal/loader/ClassLoaderValue/ClassLoaderValueTest.java test has been intermittently failing for around an year now. The failing error message states:

> Error. Agent communication error: java.io.EOFException; check console log for any additional details

This test runs in agent vm mode and it appears that the JVM crashes when this test is running, causing the agent socket communication to be lost and thus a generic error message being reported. The last few sightings of this issue, over the past year, have been reported in https://bugs.openjdk.org/browse/CODETOOLS-7903082.

The first reported sighting appears to be from JDK 19.

The latest sighting happened a few days back in my one of my personal runs and I was able to capture the core dump of the agent vm process when that happened and confirmed that this crash when the test is in progress.

So far all these crashes have been noticed only on macosx aarch64 platform.

The latest failure log shows:

#section:main
----------messages:(8/327)----------
command: main ClassLoaderValueTest
reason: Assumed action based on file name: run main ClassLoaderValueTest 
started: Wed Nov 20 01:38:58 GMT 2024
Mode: agentvm
Agent id: 30
Additional exports to unnamed modules from @modules: java.base/jdk.internal.loader
finished: Wed Nov 20 01:39:09 GMT 2024
elapsed time (seconds): 11.318
----------configuration:(13/1632)----------
...
result: Error. Agent communication error: java.io.EOFException; check console log for any additional details
...
test result: Error. Agent communication error: java.io.EOFException; check console log for any additional details
Comments
We haven't seen this crash in our CI in almost an year. I'll close this as not reproducible. Please re-open if this test crashes again.
04-11-2025
I'm seeing other strange malloc crashes in the CI e.g. * thread #3, stop reason = ESR_EC_DABORT_EL0 (fault address: 0x0) * frame #0: 0x0000000196dcae60 libsystem_malloc.dylib`nanov2_malloc_type + 160 frame #1: 0x0000000103d9c8ec libjvm.dylib`NMTPreInitAllocation::do_alloc(unsigned long) + 36 frame #2: 0x0000000103dc2f5c libjvm.dylib`os::malloc(unsigned long, MemTag, NativeCallStack const&) + 196 frame #3: 0x000000010367fda0 libjvm.dylib`AllocateHeap(unsigned long, MemTag, AllocFailStrategy::AllocFailEnum) + 80 frame #4: 0x0000000103c90cc4 libjvm.dylib`LogOutputList::set_output_level(LogOutput*, LogLevel::type) + 80 frame #5: 0x0000000103c8aacc libjvm.dylib`LogConfiguration::initialize(long) + 396 frame #6: 0x0000000103f4eee8 libjvm.dylib`Threads::create_vm(JavaVMInitArgs*, bool*) + 172 frame #7: 0x0000000103ac6c90 libjvm.dylib`JNI_CreateJavaVM + 104 This may be related to NMT changes in the VM. I'ved filed JDK-8345147
28-11-2024
I've started this off in core-libs area, where the test resides, since it's not yet clear what the root cause is.
25-11-2024