Community Forums

Home » Vuze Forums » Community Open Support


Thread: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4


Thread Locked This thread is locked - replies are not allowed.


This question is not answered. Helpful answers available: 3. Correct answers available: 1.

Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 9 - Pages: 1 - Last Post: Dec 16, 2010 4:25 AM Last Post By: catkin
catkin


Posts: 9
Registered: 02/08/10
Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 8, 2010 9:37 AM
 
Click to report abuse...
Hello :)

This issue seen with Vuze 4.3.10 and gcc-java-4.3.3-i4 running on Slackware 13.0 32-bit.

Installed Vuze 4.3.10 from Vuze_4.3.1.0_linux.tar.bz2 downloaded from Sourceforge and tested as non-root user using ~/.azureus configuration from previous 4.2.0.8. OK. Did not use for a week. Opened a torrent using Firefox 3.5.3. Saw Vuze message advising torrent had been added but Vuze exited.

Started Vuze as same non-root user in a terminal using /opt/vuze/vuze &. Saw
/opt/vuze/vuze: line 188: 8468 Aborted ${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"

Netsearched and found Linux Questions thread so, as root:
root:/var/log# ln -s /usr/lib/firefox-3.5.2/libxpcom.so /usr/lib/seamonkey/libxpcom.so
ln: creating symbolic link `/usr/lib/seamonkey/libxpcom.so': File exists
root:/var/log# echo $?
1
root:/var/log# mv /usr/lib/seamonkey/libxpcom.so /usr/lib/seamonkey/libxpcom.so.org
root:/var/log# ln -s /usr/lib/firefox-3.5.2/libxpcom.so /usr/lib/seamonkey/libxpcom.so

Tested again and got:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xa2c658f1, pid=8653, tid=2810555280
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Server VM (14.2-b01 mixed mode linux-x86 )
# Problematic frame:
# C http://libxul.so+0xa008f1

Any suggestions?

Best

Charles
catkin


Posts: 9
Registered: 02/08/10
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 18, 2010 12:52 AM   in response to: catkin in response to: catkin
 
Click to report abuse...
Upgraded to Vuze 4.3.1.4 and JRE 6u18 (was 6u16) but still have a SIGSEGV error. Tried removing ~/.azureus but same. Will now try an old version of Vuze.
Washii

Posts: 5,261
Registered: 11/14/07
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 18, 2010 3:19 AM   in response to: catkin in response to: catkin
 
Click to report abuse...
Is the SIGSEG still in libxul? That's Firefox territory.
catkin


Posts: 9
Registered: 02/08/10
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 18, 2010 3:34 AM   in response to: Washii in response to: Washii
 
Click to report abuse...
Yes it is. Firefox is "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3".

Here's the full output starting Vuze at the command line (the log file is attached):

c@CW8:/opt/vuze$ ./azureus&
[1] 7916
c@CW8:/opt/vuze$ Starting Azureus...
Suitable java version found http://java = 1.6.0_18
Configuring environment...
Java exec found in PATH. Verifying...
find: `/home/c/.azureus': No such file or directory
Browser check failed with: InvocationTargetException, No more handles Unknown Mozilla path (MOZILLA_FIVE_HOME not set)
Auto-scanning for GRE/XULRunner. You can skip this by appending the GRE path to LD_LIBRARY_PATH and setting MOZILLA_FIVE_HOME.
checking /usr/lib/firefox for GRE
GRE found at /usr/lib/firefox.
Browser check failed with: InvocationTargetException, XPCOM error -2147467259
Can't create browser. Will try to set LD_LIBRARY_PATH and hope Vuze has better luck.
setting LD_LIBRARY_PATH to: /usr/lib/firefox
setting MOZILLA_FIVE_HOME to: /usr/lib/firefox
Loading Azureus:
java -Xmx128m -cp "./Azureus2.jar:./swt.jar" -Djava.library.path="/opt/vuze" -Dazureus.install.path="/opt/vuze" -Dazureus.script="./azureus" -Dazureus.script.version=2 org.gudy.azureus2.ui.swt.Main
file:/opt/vuze/Azureus2.jar ; file:/opt/vuze/swt.jar ; file:/opt/vuze/
changeLocale: Default Language != English (United States). Searching without country..
changeLocale: Searching for language English in any country..
changeLocale: no message properties for Locale 'English (United States)' (en_US), using 'English (default)'
DEBUG::Thu Feb 18 14:08:08 IST 2010 Successfully migrated key management
UIFunctions/ImageLoad took 26ms
new shell took 210ms
new shell setup took 53ms
skinlisteners init took 0ms
skin init took 130ms
MainMenu init took 129ms
createWindow init took 0ms
skin layout took 52ms
pre skin widgets init took 26ms
hooks init took 0ms
WARNING: already added UIUpdatable com.aelitis.azureus.ui.swt.views.skin.sidebar.SideBar@2e323
skin widgets (1/2) init took 313ms
skin widgets init took 105ms
pre SWTInstance init took 0ms
Init Core Columns took 104ms
SWTInstance init took 0ms
shell.layout took 78ms
---------SHOWN AT 1266482290451;1362ms
#
  1. A fatal error has been detected by the Java Runtime Environment:
#
  1. SIGSEGV (0xb) at pc=0xa57108f1, pid=7971, tid=2810043280
#
  1. JRE version: 6.0_18-b07
  2. Java VM: Java HotSpot(TM) Server VM (16.0-b13 mixed mode linux-x86 )
  3. Problematic frame:
  4. C http://libxul.so+0xa008f1
#
  1. An error report file with more information is saved as:
  2. /opt/vuze/hs_err_pid7971.log
#
  1. If you would like to submit a bug report, please visit:
  2. http://java.sun.com/webapps/bugreport/crash.jsp
  3. The crash happened outside the Java Virtual Machine in native code.
  4. See problematic frame for where to report the bug.
#
./azureus: line 188: 7971 Aborted ${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
The 8472

Posts: 2,169
Registered: 11/13/07
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 19, 2010 3:57 PM   in response to: catkin in response to: catkin
 
Click to report abuse...
can you provide the file /opt/vuze/hs_err_pid7971.log ?
catkin


Posts: 9
Registered: 02/08/10
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 19, 2010 8:44 PM   in response to: The 8472 in response to: The 8472
 
Click to report abuse...
Thanks for asking :) AFAIK it is attached to my last post. Any difficulties accessing it, please ask again.
The 8472

Posts: 2,169
Registered: 11/13/07
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 20, 2010 8:46 AM   in response to: catkin in response to: catkin
 
Click to report abuse...
oh, my bad. didn't see it.

Well, i would assume this stems from an incompatibility between the found xulrunner library and the used swt version. You could try downloading a newer SWT library from http://download.eclipse.org/eclipse/downloads/drops/S-3.6M5-201001291300/index.php#SWT and replace the swt.jar with it.

catkin


Posts: 9
Registered: 02/08/10
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 21, 2010 5:00 AM   in response to: The 8472 in response to: The 8472
 
Click to report abuse...
Thanks :)

Following your suggestion, I downloaded swt.jar 3.631 and replaced vuze 4.3.1.4's swt.jar (3.550) with it:

c@CW8:/opt/vuze.4.3.1.4$ ll swt*
lrwxrwxrwx 1 c users 13 Feb 21 17:52 swt.jar -> swt.jar.3.631
-rw-r--r-- 1 2000 2000 1.9M Jun 12 2009 swt.jar.3.550
-rw-r--r-- 1 c users 1.4M Jan 29 17:50 swt.jar.3.631

After ensuring no Vuze files in /tmp and removing ~/.azureus (to initialise test conditions) tested again. It failed with a segmentation fault but did not, this time, show the problem analysis or produce a s_err_pid*.log. The unusual paths shown in the output are caused by resolving symlinks set to to facilitate switching between Vuze versions while testing this problem:

root@CW8:/opt# ls -ld vuze*
lrwxrwxrwx 1 root root 12 Feb 21 18:06 vuze -> vuze.4.1.0.4
drwxrwxrwx 3 root root 4096 Feb 18 14:51 vuze.4.1.0.4
drwxrwxrwx 3 root root 4096 Nov 21 2008 vuze.4.2.0.8
drwxrwxrwx 3 2000 2000 4096 Feb 8 22:23 vuze.4.3.1.0
drwxrwxrwx 3 2000 2000 4096 Feb 21 17:52 vuze.4.3.1.4

Here's the test ...

c@CW8:~$ /opt/vuze/vuze &
[1] 5382
Starting Azureus...
c@CW8:~$ Suitable java version found http://java = 1.6.0_18
Configuring environment...
Java exec found in PATH. Verifying...
find: `/home/c/.azureus': No such file or directory
Browser check failed with: InvocationTargetException, No more handles Unknown Mozilla path (MOZILLA_FIVE_HOME not set)
Auto-scanning for GRE/XULRunner. You can skip this by appending the GRE path to LD_LIBRARY_PATH and setting MOZILLA_FIVE_HOME.
checking /usr/lib/firefox for GRE
GRE found at /usr/lib/firefox.
Browser check failed with: InvocationTargetException, XPCOM error -2147467259
Can't create browser. Will try to set LD_LIBRARY_PATH and hope Vuze has better luck.
setting LD_LIBRARY_PATH to: /usr/lib/firefox
setting MOZILLA_FIVE_HOME to: /usr/lib/firefox
Loading Azureus:
java -Xmx128m -cp "./Azureus2.jar:./swt.jar" -Djava.library.path="/opt/vuze" -Dazureus.install.path="/opt/vuze" -Dazureus.script="/opt/vuze/vuze" -Dazureus.script.version=2 org.gudy.azureus2.ui.swt.Main
file:/opt/vuze.4.3.1.4/Azureus2.jar ; file:/opt/vuze.4.3.1.4/swt.jar.3.631 ; file:/opt/vuze.4.3.1.4/
changeLocale: Default Language != English (United States). Searching without country..
changeLocale: Searching for language English in any country..
changeLocale: no message properties for Locale 'English (United States)' (en_US), using 'English (default)'
DEBUG::Sun Feb 21 17:58:47 IST 2010 Successfully migrated key management
UIFunctions/ImageLoad took 0ms
new shell took 182ms
new shell setup took 52ms
skinlisteners init took 0ms
skin init took 104ms
MainMenu init took 129ms
createWindow init took 0ms
skin layout took 27ms
pre skin widgets init took 26ms
hooks init took 0ms
WARNING: already added UIUpdatable com.aelitis.azureus.ui.swt.views.skin.sidebar.SideBar@13043d2
skin widgets (1/2) init took 312ms
skin widgets init took 138ms
pre SWTInstance init took 0ms
Init Core Columns took 78ms
SWTInstance init took 0ms
shell.layout took 104ms
---------SHOWN AT 1266755329390;1315ms
/opt/vuze/vuze: line 188: 5447 Segmentation fault ${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
catkin


Posts: 9
Registered: 02/08/10
Re: Segmentation fault on startup. Vuze 4.3.10, gcc-java-4.3.3-i4
Posted: Feb 26, 2010 9:23 PM   in response to: catkin in response to: catkin
 
Click to report abuse...
catkin


Posts: 9
Registered: 02/08/10
Problem "gone away" on versions upgrade
Posted: Dec 16, 2010 4:25 AM   in response to: catkin in response to: catkin
 
Click to report abuse...
This problem "went away" running Vuze 4.5.1.0 on a fresh installation of Slackware64 13.1 including jre 6u20 (no jdk) and Firefox 3.6.12 (presumably including its own xulrunner).
Legend
Master: 800 - 9999 pts
Expert: 400 - 799 pts
Advanced: 200 - 399 pts
Intermediate: 100 - 199 pts
Beginner: 50 - 99 pts
Newbie: 0 - 49 pts
Vuze Staff Member
Vuze Community Moderator
Helpful Answer (3 pts)
Correct Answer (5 pts)

Point your RSS reader here for a feed of the latest messages in all forums