Java crash - EXCEPTION_ACCESS_VIOLATION - VMThread
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
The Java process has exited
An hs_err_pid*.log file has been created
The following appears in the
hs_err_pid*.log:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6dcf64d1, pid=4084, tid=1908 # ... snip ... --------------- T H R E A D --------------- Current thread (0x00e3cc00): VMThread [stack: 0x248d0000,0x24940000] [id=1908] ... snip ... VM_Operation (0x25d0fba0): ParallelGCSystemGC, mode: safepoint, requested by thread 0x25003000
Diagnosis
Run a memory check on the machine.
Cause
This is usually caused by a hardware error, usually in the memory. It may also be caused by a JVM bug.
Solution
Resolution
Move the instance to another machine or replace the memory.
See the more general Java crashes article for other possibilities
Was this helpful?