Open Bhumika-Khunt opened 1 year ago
Hi @Bhumika-Khunt, The JVM crashed because it failed to setup a stack for a Java thread. JVM reported out of memory.
Your process might have reached /proc/sys/vm/max_map_count
which 64k. You can check the process memory with pmap
.
Could you try to increase /proc/sys/vm/max_map_count
to 128k or 256k?
I also see you might have a lot of Java threads: 32558
_java_thread_list=0x00007f90768e66b0, length=32558, elements={
If it's true, this is too many for your host. It has only 4 cores.
I agree with @eastig in that you probably ran out of memory mappings. Every Java thread will consume two memory mappings (for the stack itself and for its guard pages). You can see this in the memory mappings of your error file (which I suppose is truncated):
...
7f8844096000-7f88440d3000 rw-p 00000000 00:00 0
7f88440d3000-7f88440d7000 ---p 00000000 00:00 0
...
0x7f88440d3000 - 0x7f8844096000 = 249856
0x7f88440d7000 - 0x7f88440d3000 = 16384
----------------------------------------
266240 = 260k
This corresponds to your 265k stack size (i.e. -Xss256K)
32558 * 2 gives 65116 mappings just for the threads and is already quite close to your 64k mappings limit.
Hi @eastig and @simonis, Thank you for your valuable inputs. Basis on the your inputs, I will increase the /proc/sys/vm/max_map_count to 128k or 256k and keep it on observation.
Hi, I am experiencing JVM crash frequently.