[Bug 437] YaCy crashed with SIGSEGV

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=437





------- Comment #3 from xerxes at zafena.se  2010-02-02 14:29 -------
>From the crash log it looks like there might be some issues with the garbage
collector. This bug might be related to the hotspot garbage colletor bugs
discussed at: http://old.nabble.com/Crash-Hotspot-td27306522.html

to summarize that discussion "there are a lot of bugs in the new garbage
collector implementations, the only one without bugs are the old serial GC
-XX:+UseSerialGC ).

Possible that the garbage collector have run out of heap.

Heap
 par new generation   total 38336K, used 34356K [0x00007f12a4910000,
0x00007f12a72a0000, 0x00007f12a72a0000)
  eden space 34112K,  88% used [0x00007f12a4910000, 0x00007f12a667d050,
0x00007f12a6a60000)
  from space 4224K, 100% used [0x00007f12a6a60000, 0x00007f12a6e80000,
0x00007f12a6e80000)     <----- !!!
  to   space 4224K,   0% used [0x00007f12a6e80000, 0x00007f12a6e80000,
0x00007f12a72a0000)
 concurrent mark-sweep generation total 4151744K, used 3352309K
[0x00007f12a72a0000, 0x00007f13a4910000, 0x00007f13a4910000)
 concurrent-mark-sweep perm gen total 45552K, used 27464K [0x00007f13a4910000,
0x00007f13a758c000, 0x00007f13a7710000)

The JVM are run with 
jvm_args: -Xms4096m -Xmx4096m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:ParallelGCThreads=2 -XX:MaxPermSize=45m -XX:ReservedCodeCacheSize=25m
-Djava.awt.headless=true 


Could you try run the jvm with the default garbage collector:
jvm_args: -Xms4096m -Xmx4096m -XX:ParallelGCThreads=2 -XX:MaxPermSize=45m
-XX:ReservedCodeCacheSize=25m -Djava.awt.headless=true 

ortry  explicitly set it to use an older implementation of garbage collector
like the SerialGC
jvm_args: -Xms4096m -Xmx4096m -XX:+UseSerialGC -XX:ParallelGCThreads=2
-XX:MaxPermSize=45m -XX:ReservedCodeCacheSize=25m -Djava.awt.headless=true 


-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.