Java Runtime Environment Fatal Error

[chace86]

I know there have been a few JVM seg faults posted in the past, but mine does not match any of the prior.

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x0000000103ca00e2, pid=655, tid=0x0000000000000307

JRE version: Java(TM) SE Runtime Environment (8.0_162-b12) (build 1.8.0_162-b12) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.162-b12 mixed mode bsd-amd64 compressed oops) Problematic frame: C [nodejavabridge_bindings.node+0x190e2] Z20getSystemClassLoaderP7JNIEnv+0x12

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

An error report file with more information is saved as: /xxx/xxx/xxx/xxx/hs_err_pid655.log

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.

• The error does not occur when I run the service locally.
• The error occurs only when I run npm test (using Jest), but only if the integration test spec runs prior to the unit test specs. If the unit test specs run before integration test spec, it works.
• I have tried adding the jinst logic to every test file, does not resolve the issue.

Is there some additional jvm argument I need or close the jvm instance?

[elwaliKa]

I'm facing exactly the same issue, if you could resolved it would please share the solution