openJDK crashes on loading eclipse galileo and the latter crashes too

Bug #563181 reported by eugenio
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x04944e32, pid=1713, tid=2996214640
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK Client VM (16.0-b13 mixed mode, sharing linux-x86 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu lucid (development branch), package 6b18~pre4-1ubuntu1
# Problematic frame:
# C [libmozjs.so+0x1ae32] js_NextActiveContext+0x16

My ubuntu version is: Ubuntu lucid (development branch) Release: 10.04 32-bit i-386

The problem occurs every time I try to load eclipse Galileo (v 3.5.2-2).

Revision history for this message
eugenio (eugenio-lacava) wrote :
Revision history for this message
avius (avi142) wrote :

It appears this also affects me, I have very similar data in the message I get:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x01685e32, pid=2039, tid=1518893936
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK Client VM (16.0-b13 mixed mode, sharing linux-x86 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu lucid (development branch), package 6b18~pre4-1ubuntu1
# Problematic frame:
# C [libmozjs.so+0x1ae32] js_NextActiveContext+0x16
#
# An error report file with more information is saved as:
# [EDIT - removed]/hs_err_pid2039.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
#

However in my case, eclipse works fine until I try to open the hints menu (ctrl + space) then this happens.
(Instead of just crashing as soon as I start the program)

Revision history for this message
avius (avi142) wrote :

not sure if this is going to help anyone, but I managed to make my bug disappear entirely
I'm not exactly sure what fixed it; eclipse was crashing as I cycled through different java vm's in eclipse startup command. Then, I began to suspect that this bug was an issue with Mozilla (due to the libmozjs in log output). I think the only relevant changes I made to my system at this point was to add the mozilla ppa and run apt update/upgrade. I didn't see any eclipse-related packages in my list of packages ready for upgrade (I only recall seeing mozilla stuff, as I had already updated/upgraded less than an hour before).
Then, I started eclipse again. As I had been doing, I pressed ctrl+space as soon as eclipse finished setting up the workspace. Instead of crashing like I expected, a dialog box popped up telling me that my content assist settings had been changed.

The program now works perfectly as far as I can see.

Revision history for this message
eugenio (eugenio-lacava) wrote :

An update, since the last run of update manager i get the following error:

 A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0049ef2d, pid=9691, tid=3078887104
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK Client VM (14.0-b16 mixed mode, sharing linux-x86 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu lucid (development branch), package 6b18-1.8-0ubuntu1
# Problematic frame:
# C [libpthread.so.0+0x7f2d] pthread_mutex_lock+0x1d
#
# An error report file with more information is saved as:
# /home/eugenio/hs_err_pid9691.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Matthias Klose (doko)
affects: openjdk-6 (Ubuntu) → eclipse (Ubuntu)
Revision history for this message
eugenio (eugenio-lacava) wrote :

I solved my issue by removing an old version of xulrunner which was causing a duplicated loading in eclicpse which in turn caused the crash as stated in this bug report: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/453188

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

"sudo aptitude remove xulrunner-1.9.1"

solved this for me (without forcing removing other packages). Probably there should be indication in eclipse packages or xulruner packages prohibiting several versions to be installed.

Revision history for this message
Benjamin Drung (bdrung) wrote :

@avius: eclipse loaded xulrunner-1.9.2.3 and xulrunner-1.9.1.9, which probably caused the problem. Can you remove one (probably the older one) of them?

We set MOZILLA_FIVE_HOME to enforce one xulrunner version (in eclipse 3.5.2-2ubuntu4). It should be possible to have different versions of xulrunner installed.

Changed in eclipse (Ubuntu):
status: New → Incomplete
Revision history for this message
Diego Garcia (diego-xaethos) wrote :

I can confirm that removing xulrunner-1.9.1 fixes this problem for me as well.

Thank goodness, too. Developing was getting tiresome with the crashes.

Revision history for this message
Niels Thykier (niels-thykier) wrote :

Hi

As far as I can tell, people found a way to fix this, so I am closing this as invalid ("best match" I could find).

Also, I noticed that some of you, who posted crash logs have shared libraries extracted into ~/.eclipse, the eclipse 3.5 (and later) from Debian + Ubuntu should not do this and may very well be the source crashes (or even future ones). Since eclipse uses the shared libraries in your ~/.eclipse there is /nothing/ we can do to fix it, other than have you remove them/your ~/.eclipse folder.

~Niels

Changed in eclipse (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.