Tag Info

New answers tagged

0

Try to run the process in 64bit mode by adding: -D64 to JVM startup flags. You can run pmap $JVMPID to see how the virtual memory is allocated. Run it before it crashes.


1

There are a few possibilities given what you've shared, for example: a leaky JNI library, or, a thread-creation leak, or leaky dynamic code proxies (perm-gen leak), but I can only make a guess because you didn't provide any log output, or indicate whether the JVM was throwing an OutOfMemoryException (OOM), or if some other fault was encountered. Nor did ...



Top 50 recent answers are included