Jvm crash .. not enough free memory? (1.6)

Question

I got this from the crash log .. it looks like free memory is super low (1020k), which is caused by too little memory?

I have 10 gram RAM and my GC settings: -Xmx5g -XX:NewRatio=3 -XX:CMSInitiatingOccupancyFraction=70 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseAdaptiveSizePolicy -XX:MaxGCPauseMillis=700 .

Can someone please give me some advice? Thanks!

 # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f220198ce10, pid=26470, tid=1154627904 # # JRE version: 6.0_24-b07 # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # J com.twitter.typeahead.server.topic.TopicTypeAheadController$2.onSuccess(Lcom/twitter/typeahead/common/MetastoreResult;)V # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Current thread (0x00007f21f2ce0800): JavaThread "New I/O client worker #1-18" [_thread_in_Java, id=26628, stack(0x0000000044c23000,0x0000000044d24000)] siginfo:si_signo=SIGSEGV: si_errno=0, si_code=2 (SEGV_ACCERR), si_addr=0x00007f2200e4616a Registers: RAX=0x00000006bae61950, RBX=0x00000007fafe2be0, RCX=0x0000000000000000, RDX=0x00000006bbe2d580 RSP=0x0000000044d22180, RBP=0x00000006bae61950, RSI=0x00000006bae61950, RDI=0x00007f220198ccf0 R8 =0x00000000d77c5ab0, R9 =0x00000006bbd0a190, R10=0x00000000035df16a, R11=0x00007f21fd867000 R12=0x0000000000000000, R13=0x0000000044d22180, R14=0x0000000000000001, R15=0x00007f21f2ce0800 RIP=0x00007f220198ce10, EFL=0x0000000000010207, CSGSFS=0x0000000000000033, ERR=0x0000000000000006 TRAPNO=0x000000000000000e Register to memory mapping: RAX=0x00000006bae61950 [error occurred during error reporting (printing registers, top of stack, instructions near pc), id 0xb] Stack: [0x0000000044c23000,0x0000000044d24000], sp=0x0000000044d22180, free space=1020k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) 

Answer 1

I don’t think you are running out of memory. This is a bug for segfault in the JVM.

Try reading these stackoverflow posts. They should point you in the right direction:

Java VM: playable SIGSEGV on 1.6.0_17 and 1.6.0_18, how to report?

how to debug SIGSEGV in jvm GCTaskThread

Well, if the JVM does not have an error when it attacks segfault or buffer overflow without a first failure with insufficient remaining stack memory, try setting the -Xss value (stream stack size) to a higher value.