[Bug 437] YaCy crashed with SIGSEGV

[bugzilla-daemon at icedtea.classpath.org]

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





------- Comment #14 from xerxes at zafena.se  2010-02-02 20:15 -------
what you experience in comment #12 and #13 sounds like normal out of memory
issues when a java application allocates all available RAM (and swap) on a
system.

You have to check with the yacy community to see if yacy can be configured to
not use more ram than you actually got installed in your system. You might
solve your memory issues by simply specifying a lower -Xms and -Xmx value when
starting the jvm, for example if you got 2Gb of physical ram installed then
dont specify more than -Xms2048m -Xmx2048m or else you will start running on
swapspace in no time (slow noisy and makes your system unresponsible and when
it runs out then you start see the cant run program errors) .

ok back to the real bug (the SIGSEGV jvm crash) ... im happy to see that you do
not get any hotspot jvm crashes when running using the default garbage
collector options and serial gc option, this probably means that there are
something broken with the -XX:+UseParNewGC -XX:+UseConcMarkSweepGC but we
really dont know unless we have it reproducable running under a debugger. 

please file a new bug if you experience other kinds of bugs than the SIGSEGV
jvm crash.


-- 
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.