|Summary:||[poi 3.8 beta 3]compiler thread bringing instance down|
|Component:||XSSF||Assignee:||POI Developers List <dev>|
Description Basil 2014-08-27 18:50:24 UTC
# A fatal error has been detected by the Java Runtime Environment: # # java.lang.OutOfMemoryError: requested 17179869200 bytes for Chunk::new. Out of swap space? # # Internal Error (allocation.cpp:215), pid=31328, tid=1110718784 # Error: Chunk::new # # JRE version: 6.0_20-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode linux-amd64 ) # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # --------------- T H R E A D --------------- Current thread (0x000000004062c800): JavaThread "CompilerThread1" daemon [_thread_in_native, id=31343, stack(0x0000000042243000,0x0000000042344000)] Stack: [0x0000000042243000,0x0000000042344000], sp=0x000000004233d500, free space=3e90000000000000018k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) Current CompileTask: C2:8428 ! org.apache.poi.ss.util.SheetUtil.getColumnWidth(Lorg/apache/poi/ss/usermodel/Sheet;IZ)D (799 bytes) This is trying to use 17gb of swap and killing instance
Comment 1 Basil 2014-08-27 18:51:26 UTC
This is bringing our production instances down.
Comment 2 Nick Burch 2014-08-27 18:54:19 UTC
Firstly, please try with a more recent version of Apache POI (eg 3.11 beta 2) Secondly, you seem to be using an old version of Java, so try upgrading to the latest one (for Java 6 that's update 45). I doubt anyone on the JVM team will be too worried about crashing an old version, you'll need to be on the latest to get them to investigate
Comment 3 Dominik Stadler 2015-09-13 20:44:03 UTC
A crash is never a problem in POI itself, but more likely a problem in the JVM itself or any piece of native software that you load into the JVM, therefore closing this as WORKSFORME here.