Eclipse crashes at start in karmic 64bits

[Andres Mujica]

eclipse
searching for compatible vm...
  testing /usr/lib/jvm/default-java...found
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fcd519fb2ae, pid=5782, tid=140521219340624
#
# JRE version: 6.0-b16
# Java VM: OpenJDK 64-Bit Server VM (14.0-b15 mixed mode linux-amd64 )
# Distribution: Ubuntu karmic (development branch), package 6b16~pre4-0ubuntu6
# Problematic frame:
# C [libxul.so+0x63e2ae]
#
# An error report file with more information is saved as:
# /home/andres/hs_err_pid5782.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.
#

ProblemType: Bug
Architecture: amd64
Date: Fri Jul 17 23:19:08 2009
DistroRelease: Ubuntu 9.10
Package: openjdk-6-jre 6b16~pre4-0ubuntu6
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SourcePackage: openjdk-6
Uname: Linux 2.6.31-999-generic x86_64

[Andres Mujica (andres.mujica)]

confirmed based on duplicate report.

It seems related to xulrunner.

[Onkar Shinde (onkarshinde)]

Which version is 4.1? AFAIK, the latest eclipse version is 3.5.

[Andres Mujica (andres.mujica)]

/me scratching my head about 4.1 ... where did it came from?

[Ludovic Claude (ludovicc)]

Assign to Eclipse package as this bug affects only Eclipse

[Michele Mordenti (micmord)]

I have no problem with eclipse 3.5 (not .deb) on my 64bit kamic with sun-java6-jdk
The actual eclipse version on karmic is 3.4.1-0ubuntu2 affected by bug 401402

IMHO this is an invalid bug

[Michele Mordenti (micmord)]

Ummhh... possible that 4.1 cames from 3.(4.1) ?

[Andres Mujica (andres.mujica)]

ohh my... what i was thinking.... is not 3.5 is 3.4.1 .. the recent updated eclipse version from the repos.. that's why i filled the bug...

i must test again... if i'm not wrong is not working at all.. some clash between vuze and eclipse dependencies

let me check it tonight

[JockeTF (jocketf)]

I have the same problem in Karmic 32-bit. It doesn't crash at start but with the same error after a few minutes of usage.

[Benjamin Drung (bdrung)]

Is this bug fixed in eclipse 3.5.1-0~ubuntu1?

[sheldonross (ross-sheldon)]

This bug is still present in 3.5.1, I believe it to be a xulrunner bug, not an eclipse bug...

[sheldonross (ross-sheldon)]

Here is a log from my system up-to-date as of today with a wiped .eclipse directory, and fresh workspace.

[sheldonross (ross-sheldon)]

Removal of xulrunner (along with firefox and everything else :( ) Seems to fix the issue.

[sheldonross (ross-sheldon)]

Installed firefox 3.6 from the daily ppa, and by extension xulrunner 1.9.2xxx. And my eclipse nolonger crashes.

[sheldonross (ross-sheldon)]

I suppose that maybe eclipse is not using that package/library though, so it may not have actually resolved the issue.
But I have a working eclipse, and a working firefox (although beta) so I'm content for the moment.

[Benjamin Drung (bdrung)]

Can you retry with eclipse 3.5.1-0ubuntu4?

[Zaki Manian (zmanian)]

I just tested on eclipse 3.5.1-0ubuntu4 and I am not seeing problem

On Sun, Oct 18, 2009 at 12:10 AM, Benjamin Drung
<email address hidden>wrote:

> Can you retry with eclipse 3.5.1-0ubuntu4?
>
> --
> Eclipse crashes at start in karmic 64bits
> https://bugs.launchpad.net/bugs/400962
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Benjamin Drung (bdrung)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.