Segmentation Fault during startup
 

Hi,

I installed Version 2.02 of Limewire. During startup I see the splash screen and then I get the following error message:
"./runLime.sh: line 4: 4213 Segmentation Fault java -jar RunLime.jar"
I have jre 1.3.1_02 installed.
What can I do?

Download a newer beta, I believe version 2.1.1 is out now. You could also download Sun's j2sdk 1.4 beta.

Did this work for you?
 

I'm haveing the same problem I'm running Mandrake 8.0 and JRE1.3.1_02 Is there anyother help for this problem any would be greatly appreciated! :D

Hapy Days! oh joy! oh Rapture!!!!
 

Hey if you haven't figured this out yet I think I just found the answer in a thread down below try this out. I'll try it tonight and let you know.:D
-----------------------------------------

:o
!!!! FIX !!!
in the java 1.3.1 release notes, i found this:

* For Linux users - The newer glibc-2.2.x libraries cannot correctly handle initial thread stack sizes larger than 6 MB. This can cause a segmentation fault on come Linux platforms that use the newer libraries. Such platforms include Red Hat 7.0, Mandrake 8.0, SuSe 7.2, and Debian 2.2. The problem will not occur on Linux platforms that are using glibc-2.1.x such as Red Hat 6.1 and 6.2. It will also not affect Red Hat 7.1 because it uses a different thread stack layout. This problem is being tracked as bug 4466587.

Workaround - Use "ulimit -s 2048" in bash shell or "limit stacksize 2048" in tcsh to limit the initial thread stack to 2 MB.

i added the line "ulimit -s 2048" to runlime.sh just before the call of java and now it works!

hope this will help you, too!

wingo
------------------------------------------------------
:D

Great! It works.

Thanks a lot.

Yup, Worked for me too! Glad I could help. :cool:

Just more information on the condition: I had no problems using Limewire 1.7c. When I tried the next version, 1.8, I got this segfault. It still exists as of 2.1.3, but the "ulimit -s 2048" workaround resolves the segfault. I have Glibc 2.2.1 and Sun's jre1.3.1_02. As such, something was changed between Limewire versions 1.7c and 1.8 to wake the dormant segfault, or create it.

Greg

yippie skippie
 

me rykie wery muchie

Just to let you know that this problem also affects RH 7.1 running LimeWire 2.2. It may not affect any other java programs though.

thanks jalmon
 

that darned seg fault caused me a lot of problems.
thanks for the help jalmon. I guess I should have read EVERYTHING - i.e. release notes for the java

penguin@cox-internet.com