Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Help!!! JVM crash
See original GitHub issueproject start log:
- A fatal error has been detected by the Java Runtime Environment:
- SIGILL (0x4) at pc=0x00007f1d77a496d0, pid=193, tid=0x00007f1e2d43b700
- JRE version: Java™ SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11)
- Java VM: Java HotSpot™ 64-Bit Server VM (25.131-b11 mixed mode linux-amd64 compressed oops)
- Problematic frame:
- C [libtensorflow_framework.so.2+0x160d6d0] nsync::nsync_mu_init(nsync::nsync_mu_s_*)+0x0
- Core dump written. Default location: /home/core or core.193
- An error report file with more information is saved as:
- /home/hs_err_pid193.log`
hs_err_pid193.log:
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
6 Crashing JVM - Oracle Help Center
A JVM crash could be caused by a programming error in the JRockit JVM or by errors in third-party library code. Identifying and...
Read more >How To Diagnose And Prevent Java (JVM) Crashes - Xperti
If Java crashes while generating a code, the most common reason could be an error during method compilation. If the JVM does not...
Read more >How do I investigate the cause of a JVM crash? - Stack Overflow
Generally, JVM crashes are pretty hard to diagnose. They could happen due to a bug in some JNI code or in the JRE...
Read more >How We Diagnosed a JVM Crash - New Relic
When all the JVMs in our distributed application quit unexpectedly one day, the New Relic Browser team diagnosed a JVM crash.
Read more >Diagnosing a JVM Crash! - The Java Advent Calendar
Common causes of JVM Crash · Running out of native memory. This is caused when native memory is exhausted, read more about native...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You should be able to compile from source and specify the instructions available on your docker host. I think by default the newest thing we target is AVX, so presumably that’s missing in your docker environment.
Seems to be a bug in nsync and/or devtoolset: https://stackoverflow.com/questions/64408047/illegal-instruction-0x00007ffff3712210-in-nsyncnsync-mu-initnsyncnsync-mu