Regarding the error A fatal error has been detected by the Java Runtime Environment:
1. Overview of error reporting
# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000, pid=2608, tid=0x00002504 # # JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11) # Java VM: Java HotSpot(TM) Client VM (25.131-b11 mixed mode windows-x86 ) # Problematic frame: # C 0x00000000 # # Core dump written. Default location: C:\Users\Administrator\Desktop\aerotop-led-project\hs_err_pid2608.mdmp # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
Today, when running the Java program, I reported an error as shown above, and then check the log. Through query on Baidu, I gave several solutions that can not completely solve the error, but still report an error. When looking down at the log, I found the usage of JVM heap memory and meta space, as shown below:
Heap: def new generation total 44672K, used 13804K [0x05000000, 0x08070000, 0x0a550000) eden space 39744K, 30% used [0x05000000, 0x05bab018, 0x076d0000) from space 4928K, 37% used [0x07ba0000, 0x07d70208, 0x08070000) to space 4928K, 0% used [0x076d0000, 0x076d0000, 0x07ba0000) tenured generation total 98972K, used 59381K [0x0a550000, 0x105f7000, 0x15000000) the space 98972K, 59% used [0x0a550000, 0x0df4d4f0, 0x0df4d600, 0x105f7000) Metaspace used 63522K, capacity 65876K, committed 66048K, reserved 66944K
Although no oom error is reported, there is still a fluke to change the size of heap memory and meta space, but an error is still reported.
2. Solution:
# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000, pid=2608, tid=0x00002504 # # JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11) # Java VM: Java HotSpot(TM) Client VM (25.131-b11 mixed mode windows-x86 ) # Problematic frame: # C 0x00000000 # # Core dump written. Default location: C:\Users\Administrator\Desktop\aerotop-led-project\hs_err_pid2608.mdmp # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
In the initial log message, a keyword problem frame is found: the file name is displayed below, so it is located in the file. It is found that it is caused by the method used to process multiple scheduled tasks at the same time, resulting in an error. After modifying the program, solve the problem.
Similar Posts:
- Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
- [Solved] Database Install Error: An unexpected error has been detected by HotSpot Virtual Machine
- eclipse.ini/myeclipse.ini -Xms,-Xmx,-PerSize
- Multiple JDK switch and solution of could not find java.dll exception in win10 environment
- Eclipse failed to create the java virtual machine [How to Solve]
- Ubuntu16.04: How to Solve “no java virtual machine was found after searching the following locations:” Error
- [How to Use] System.getProperty(“user.dir”)
- An error is reported when eclipse uses gradle to build the system
- Investigation on the error caused by: java.lang.outofmemoryerror: Java heap space of Tomcat Java application in production environment