Eclipse SEGFAULTs in libgtk-x11: gtk_tooltips_set_tip()

[Fabian Köster]

Eclipse crashes, reproducibly.

From the hs_err_pidXXXXX.log:

...
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000008
...
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libgtk-x11-2.0.so.0+0x2593dc] gtk_tooltips_set_tip+0x1dc
C [libswt-pi-gtk-3236.so+0x39984] Java_org_eclipse_swt_internal_gtk_OS__1gtk_1tooltips_1set_1tip+0xa4
j org.eclipse.swt.internal.gtk.OS._gtk_tooltips_set_tip(II[B[B)V+0
j org.eclipse.swt.internal.gtk.OS.gtk_tooltips_set_tip(II[B[B)V+11
j org.eclipse.swt.widgets.Shell.setToolTipText(ILjava/lang/String;Ljava/lang/String;)V+142
...

[Fabian Köster (maestro-alubia)]

Additional information: I am using Gutsy

Appending java log-file

[Jonathan Anderson (jonathan-anderson)]

Confirmed; I have this exact problem when running Eclipse. I'm using CDT + Qt integration, but that doesn't have anything to do with gtk_tooltips_set_tip.

[Jonathan Anderson (jonathan-anderson)]

I don't see this problem when I run Eclipse Europa from eclipse.org... perhaps a revbump would take care of this? MOTUs?

[hexion (hexium)]

More apps based on Java are crashing...
http://ubuntuforums.org/showthread.php?t=511991

[hexion (hexium)]

In my box, I discovered that eclipse crashes always when I put the mouse over the name of an opened file in the selection of files area.

[Charles Goodwin (charlesgoodwin)]

Ok, for me it crashes whenever I mouseover the 'x' on a file tab, every time.

[saads (shakhshir)]

same here - every time I mouseover the 'x' on a file tab.

[Joe Barnett (thejoe)]

by adding "&& tooltipsdata" to the if statement on line 213 of gtk/gtktooltips.c in gtk+, this no longer segfaults eclipse

[Charles Goodwin (charlesgoodwin)]

Running a vanilla eclipse package from www.eclipse.org does not crash...

[Murray Cumming (murrayc)]

This is indeed very annoying.

This is probably related to the deprecation of the GtkTooltips API in GTK+ 2.12, in favour of the GtkTooltip (no s) API. Of course it shouldn't cause a crash or change of behaviour. Maybe Eclipse is using the API in some way that it shouldn't.

[hexion (hexium)]

Vanilla eclipse (3.3 version) doesn't crash here.

It wont work with the default VM (/usr/lib/jvm/java-gcj/jre/bin/java) , so install another and start eclipse with it:
In example, after installing sun-java6-jdk package:

/opt/eclipse3.3/eclipse -vm /usr/lib/jvm/java-6-sun/jre/bin/java

Yes, I know, installing 3rd party packages doesn't help ubuntu's development process... BUT many of us need eclipse TO WORK, and simply cannot wait another 2 months for this to be fixed.
The other alternative is to install again Feisty and stop testing Gutsy... so this is "less bad"

[Steffen Rusitschka (rusi)]

Joe Barnet - thanks alot, that did the trick! (https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/128232/comments/8)

[Matthijs De Smedt (matthijs--)]

So could someone upload a non-crashing libgtk-x11-2.0.so ? I desperately need to run an older version of Eclipse (JBoss 2.0.0beta2) which has this problem.

[Matthijs De Smedt (matthijs--)]

I have patched (Joe Barnett's patch) and compiled libgtk+2.0 2.11.6-1ubuntu4 myself from source (http://packages.ubuntu.com/gutsy/source/gtk+2.0). Attached is the resulting libgtk-x11-2.0.so binary.

If you want to run Eclipse normally (for the time being) I STRONGLY recommend you to get the latest Eclipse Europa packages from eclipse.org

If, like me, you have to run an older version of Eclipse, you can try my patched lib. It works for me, but obviously I cannot guarantee it'll work for you. Don't blame me if you can't boot into Gnome anymore.

To install:
sudo rm /usr/lib/libgtk-x11-2.0.so.0
sudo ln -s /usr/lib/libgtk-x11-2.0.so.0.1106.0-matthijs /usr/lib/libgtk-x11-2.0.so.0

To uninstall:
sudo rm /usr/lib/libgtk-x11-2.0.so.0
sudo ln -s /usr/lib/libgtk-x11-2.0.so.0.1106.0 /usr/lib/libgtk-x11-2.0.so.0

[Murray Cumming (murrayc)]

Kristian Rietveld (The GTK+ tooltips developer) said
"
I think this has been fixed already, only the patch is in a post 2.11.6
release. If somebody could test if eclipse still crashes with trunk,
that would be great. (It's under #460194 in our bugzilla).
http://bugzilla.gnome.org/show_bug.cgi?id=460194
"
in
http://mail.gnome.org/archives/gtk-devel-list/2007-September/msg00024.html

[Sebastien Bacher (seb128)]

Not sure if Kristian speaks about the change on http://svn.gnome.org/viewcvs/gtk%2B?view=revision&revision=18587 but the gutsy package already has this patch, there is no tooltips change in the SVN since this one

[Matthijs De Smedt (matthijs--)]

>
> Not sure if Kristian speaks about the change on
> http://svn.gnome.org/viewcvs/gtk%2B?view=revision&revision=18587 but the
> gutsy package already has this patch, there is no tooltips change in the
> SVN since this one

 Then I don't think SVN HEAD has the fix as found by Joe Barnett. Which
according to SVN HEAD should be inserting "&& tooltipsdata" at line 234.

[Matthijs De Smedt (matthijs--)]

Can the maintainer of GTK+ please include the patch? It's a really simple fix which solves this problem. I attached the diff (for libgtk2.0-0 2.11.6-1ubuntu4).

[Havoc][ (kubuntu-actinoide)]

Whats about this Bug? I get the same Error - my Eclipse is crashing about 10 Times per Day. Are there any purpose to add the patch from Matthijs?

[Havoc][ (kubuntu-actinoide)]

PS. The Patch from Matthijs works for me.

[octoberdan (octoberdan)]

Patch worked for me as well. Thanks Matthijs.

[Steffen Rusitschka (rusi)]

Still the same problem with the latest update to 2.12.0-0ubuntu1 - the patch still works, however

[Peter Schwenke (bluetoad)]

Another "me too". If you slowly click on a tab for one of the open files it seems to be OK. So if you wait for the
tooltip to come up or maybe just before it comes up.
But when you forget and go to one of the tabs and click - kaboom!

Patch solves it.

[jens (j-schuerks)]

Patch doesn't work on amd64, compiling from source didn't help either. I'm stuck. Any suggestions?

[jens (j-schuerks)]

Sorry wrong statement. Compiling from source helps

[octoberdan (octoberdan)]

An upgrade killed the fix and eclipse is once again crashing. This is true for the standalone and ubuntu package. I just reapplied the libgtk-x11-2.0.so.0.1106.0-matthijs fix. I will let you know if it helps.

Why isn't the fix being pushed? Having a broken widely used package is a little severe...

[Sebastien Bacher (seb128)]

that's not clear the issue is due to GTK and gutsy is not stable yet so there is time to work on it, if you need a totally working system you should maybe consider using a stable version of Ubuntu

[Matthijs De Smedt (matthijs--)]

This is now fixed upstream.

http://bugzilla.gnome.org/show_bug.cgi?id=460194#c18
http://svn.gnome.org/viewcvs/gtk%2B/trunk/gtk/gtktooltips.c

[Sebastien Bacher (seb128)]

The change has already been uploaded to Ubuntu some hours ago it's just blocked by the beta freeze for now

[Sebastien Bacher (seb128)]

gtk+2.0 (2.12.0-1ubuntu2) gutsy; urgency=low

  * debian/patches/080_from_bugzilla_workaround_eclipse_crash.patch:
    - patch from bugzilla, workaround eclipse crasher (LP: #128232)

 -- Sebastien Bacher <email address hidden> Mon, 24 Sep 2007 15:18:00 +0200

[Manuel Zach (loogaroo)]

this problem is now fixed for me, on gutsy with the latest upgrades (1st Oct. 07)
thx a lot.

[Chris Snyder (csnyder)]

Unfortunately, I'm still seeing this problem with the latest Gutsy libgtk. It seems to be less common than before the update. I'm not getting hs_*.log files right now, so I'm not able to give an exact description at the moment. The behavior seems similar, however (it usually happens when I'm dragging something in the package explorer, which was the case before as well).

I'll try to get a log file, and will post here if it seems related or start a new bug (if needed) if it's not.

[hexion (hexium)]

Chris, maybe your problem has something to do with this bug I reported:
https://bugs.launchpad.net/ubuntu/+source/bug-buddy/+bug/146332

Uninstall temporally bug-buddy.. and if you don't experience more crashes with Eclipse after doing that, report it in that bug.

[Peter Schwenke (bluetoad)]

Definitely seems to be fixed.

[Shawn Willden (shawn-ubuntu-willden)]

I'm seeing this behavior with IBM's Rational Software Architect on Gutsy AMD64. It looks like the issue is the same, but it's not from the 64-bit libgtk2. Instead, it's from the 32-bit libgtk2 installed by the ia32-libs package. I'm going to patch and rebuild and see if that fixes it. Unfortunately, the ia32-libs package is almost 400MB of source code, so it's going to take a while to rebuild and test.

[Shawn Willden (shawn-ubuntu-willden)]

Updating ia32-libs solved the problem.

[Shawn Willden (shawn-ubuntu-willden)]

And, of course, after I spent two hours downloading and figuring out how to update ia32-libs, this morning there's a fresh ia32-libs coming down in the day's updates :)

If your Gutsy is up to date, this bug should be gone.

[Julia (julia-whalespout)]

My Gutsy is up to date, but I was still having the problems described about, where anything I did caused stand alone Aptana to crash. I just updated through the program's update tool, and it stayed open longer. However, when I try to open a project, I get this:
JVM terminated. Exit code=1
/usr/bin/java
-Xmx384M
-Xms128M
-Djava.awt.headless=true
-jar /home/user/aptana/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /home/user/aptana/Aptana
-name Aptana
-showsplash 600
-exitdata 230002
-vm /usr/bin/java
-vmargs
-Xmx384M
-Xms128M
-Djava.awt.headless=true
-jar /home/user/aptana/startup.jar

...And Aptana closes. Since things were apparently fixed already, I don't know if I should try the solution above or what.

[Niels Thykier (niels-thykier)]

Hi

Can this be reproduced using eclipse 3.5.1-0ubuntu3 from the Ubuntu repositories?

~Niels

[Benjamin Drung (bdrung)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!