Community
Participate
Working Groups
When I try to create a class in a new, empty project, Eclipse M5 under Linux/GTK crashes. I get the following assertion violation message from the theme engine I'm using (crux, Debian unstable, gtk2-engines-crux 2.2-3): ** (<unknown>:8306): CRITICAL **: file crux-draw.c: line 1017 (draw_box): assertion `width < 32768' failed ** (<unknown>:8306): CRITICAL **: file crux-pixmaps.c: line 419 (eazel_engine_image_render): assertion `width > 0' failed The Eclipse crash log, which appears after this message, is attached to this report. Thanks for looking into this, and thanks for an awesome product!
Created attachment 3516 [details] crash log
... I just verified that this crash does not occur when I use the GNOME default theme, rather than Crux. I will file an additional bug report to the maintainers of the Debian package, gtk2-engines-crux.
I just talked to a user on #eclipse who encountered the same exact problem.
I can certify all. I'm the user of exposed the crash to #eclipse irc channel, and yes only happens with crux theme. I tested with default gnome2-2 theme, gran canyon, oceanic dream...etc and with all of these, eclipse opens well the java editor, but with crux theme the eclipse IDE crashes. Thanks to Andre, Jed an #eclipse irc channel for helping me (a today's new eclipse user-and a great newbie java student) to determine the cause of the crash. Thanks also to Andre for posting the bug.
I have another bug on progressBar/Gtk2.2.1/Theme Crux/. See Bug#32204
This is a repeat of bug number 29795 and was identified as a Debian problem. The bug was submitted to debian and identified as an upstream problem. (bug number 180722) The fun part is that I no longer have the problem with RC2 on unstable :) and gnome hasn't addressed this bug. Also the progress bar (Bug#32204, as mentioned above) doesn't appear to be applicable on unstable at the time of writing
I would add that I get the same error with the progress bar when installed the Redhat phoebe beta. It uses the Blueburve theme as default.
On the new Mandrake, the default theme is Galaxy, and the segfault does happen there, and also on a few other themes. Though I was able to find themes not causing the segfault, those are nice but weird enough looking for using them for extended periods of time; so I decided to do a little further digging to see what could be done. I hoped that I would debug a simple test case and just fix it. It turns out that test cases, and the ControlExample, do not cause a GP. Also, there are many places where Eclipse uses the native progress bar, but it only GPs occasionally. This is interesting because this is not the behavior I saw half a year ago (it was *always* crashing in set_fraction). The appends above indicate BlueCurve is a "bad" theme. I've never seen it crash on the RH8.0/BlueCurve box in my office, I conclude that there is some randomness. Btw, Crux is "good" on my Mdk box - go figure. Also, I re-read the code and it is straightforward, not giving many chances for mistake. The calls look fine, and I also inspected the relevant parts of swt.c - we are coercing types correctly. My conclusion is that the problem is not localized around the set_fraction() - maybe trashing memory somewhere else.
Sometimes the crash leaves you with a totally hosed workspace. You re-launch Eclipse, and scrolling is really cheesy (looks like having two trees showing through each other), and you can't quit (saying OK just leaves you there). However, bringing the workspace from Mdk to RH (with BlueCurve), it comes up fine.
*** Bug 35743 has been marked as a duplicate of this bug. ***
The problem is now gone for me, using Eclipse RC3a and an updated version of the Crux theme (gtk2-engines-crux 2.2.1-2, Debian unstable). I do get occasional messages in the terminal: ** (<unknown>:1817): CRITICAL **: file crux-draw.c: line 1020 (draw_box): assertion `height >= -1' failed but Eclipse keeps running just fine.
*** Bug 35946 has been marked as a duplicate of this bug. ***
*** Bug 36283 has been marked as a duplicate of this bug. ***
Created attachment 4567 [details] Mandrake 9.1 hs file I removed the file /usr/lib/gtk-2.0/2.2.0/engines/libgalaxy.so as described in bug 35946 and it works fine on mandrake 9.1 this will bring up the 2.0.x look but this one doesn't seem to crash A easy way to recreate the problem is - create eclipse unzip from 2.1 Release, cd into eclipse folder, start eclipse - create a new java project named ant - select yes when it ask to to open the java view after creating the project - rigth click and select team share - fill the values anoncvs cvanoncvs s.apache.org /home/cvspublic - click next type ant on the module name - eclipse will crash when you press ok.
*** Bug 36417 has been marked as a duplicate of this bug. ***
*** Bug 36572 has been marked as a duplicate of this bug. ***
Created attachment 4624 [details] Crash log under Red Hat 9 This is the log generated when trying to do [Navigator] Team -> Share Project -> [Select repository] -> Finish under Red Hat 9 with the default theme (BlueCurve) and configuration.
*** Bug 36911 has been marked as a duplicate of this bug. ***
Hi all, first vote ever for a bug here, excuse me if I do something wrong. I confirm I have the gtk_progress_bar_set_fraction bug on a stock RedHat 9 installation on a PC, with JDK 1.4.1_02 and Eclipse 2.1. It crashes Eclipse with a signal 11 if I use the Crux theme. I noticed it while using EclipseUML from Omondo. If I change to another theme, there's no problem. Thanks for that wonderfull "thing" Eclipse is... I use it professionnally on a daily basis.
fixed > 20030428
Felipe, please patch this into the R2_1_maintenance stream.
Fixed in HEAD and R2_1_maintenance. I've tested the changes in RedHat 9.0/Bluecurve theme and I know it works, but it would be nice with a mandrake user could download the last integration build (I20030429) and give a try. I believe Mandrake 9.1/Galaxy theme has the same problem. Thanks.
*** Bug 37482 has been marked as a duplicate of this bug. ***
*** Bug 37632 has been marked as a duplicate of this bug. ***
*** Bug 38230 has been marked as a duplicate of this bug. ***
*** Bug 38544 has been marked as a duplicate of this bug. ***
*** Bug 37202 has been marked as a duplicate of this bug. ***
*** Bug 47818 has been marked as a duplicate of this bug. ***
I have the same problem on: Mandrake 9.2 rpm -qa | grep libgdk give: libgdk_pixbuf2.0_0-2.2.4-2mdk libgdk-pixbuf2-0.22.0-2mdk rpm -qa | grep gtk give: libgtk+-x11-2.0_0-2.2.4-2mdk libgtk+2.0_0-2.2.4-2mdk gtkdialogs-2.0-6mdk gtk-engines-0.12-8mdk libgtk+1.2-1.2.10-37mdk libgtkxmhtml1-1.4.2-7mdk gtk+2.0-2.2.4-2mdk rpm -qa | grep eclipse give: eclipse-gtk2-2.1.0-2jpp eclipse-platform-2.1.0-2jpp eclipse-scripts-2.1.0-2jpp eclipse-jdt-2.1.0-2jpp eclipse-gtk2-2.1.0-2jpp When i: - create eclipse unzip from 2.1 Release, cd into eclipse folder, start eclipse - create a new java project named what_ypu_want - select yes when it ask to to open the java view after creating the project - rigth click and select team share - fill the values anoncvs cvanoncvs s.apache.org /home/cvspublic - click next type ant on the module name - eclipse will crash when you press ok. with first message: Current Java thread: at org.eclipse.swt.internal.gtk.OS.gtk_progress_bar_set_fraction(Native Method) - locked <0x54b6d510> (a java.lang.Class) ... If this is resolved (like show on Staus), what can we do???
Pavie, check comment#22. It might be possible that changing the theme fixes the problem (I'm supposing you are using Galaxy).
I use 2 others theme: default theme (which it's not Galaxy) Nostalgie And i've always the same bugs... Should i avoid to use KDE, or which theme should be ok??? Benjamin
I try with Icewm and always the same things...
Pavie, I was checking and it's very likely that this version of Eclipse you are running does not include the fixes for this problem. This bug was marked fixed for R_2_1_maintenance on 2003-04-29 (see comment #22), Eclipse 2.1 was released Thu, 27 Mar 2003 (see Eclipse.org/download/) Therefore, you should upgrade your Eclipse to 2.1.1, 2.1.2, or 3.0 M6. You should be able to use the Eclipse update mechanism to update eclipse from 2.1.0 to eclipse 2.1.1 or even 2.1.2. Note: I'm supposing this RPM you used to installed Eclipse uses the code base from Eclipse 2.1.0.
Ok, i have the last updtae and all is oK... Sorry to have reopen this bug, it should be close for me Benjamin for information: On mandrake 9.2, the rpm to install are: rpm -qa | grep eclipse eclipse-jalopy-1.0-0.b10.3jpp eclipse-gtk2-2.1.2-6jpp eclipse-platform-2.1.2-6jpp eclipse-jdt-2.1.2-6jpp eclipse-legacymenu-2.1.2-6jpp eclipse-mdkmenu-2.1.2-6jpp eclipse-scripts-2.1.2-6jpp Thanks for all!!!
closing bug
On SuSE 9.1, the problem is back with RC1. To solve the issue, check the dump. There should be a line which contains "/engines/": 4ddf9000-4de04000 r-xp 00000000 03:05 187723 /opt/gnome/lib/gtk-2.0/2.2.0/engines/libqtpixmap.so I just renamed this file to "libqtpixmap.so.buggy" and started Eclipse again. Now, I get lots of warnings on the console: (<unknown>:5383): Gtk-WARNING **: /opt/gnome/lib/gtk-2.0/2.2.0/engines/libqtpixmap.so: cannot open shared object file: Datei oder Verzeichnis nicht gefunden but at least Eclipse works.
Aaron, why you don't choose a different theme what doesn't use libqtpixmap.so engine ?
Re #37 I don't know how :-)
