Community
Participate
Working Groups
Created attachment 246176 [details] hs_err file When renaming a class and often, but not always, when renaming a variable, Eclipse crashes. I am using Luna Release (4.4.0), build 20140612-0600 on Crunch Bang (Debian 7 wheezy). I have attached the hs_err file after a crash when renaming a class.
What is the GTK/cairo version in use? Can you provide an swt only reproducer to ease reproducing problem?
(In reply to Alexander Kurtakov from comment #1) > What is the GTK/cairo version in use? libcairo2 is version 1.12.2-3, libgtk2.0-0 is 2.24.10-2, libgtk-3-0 is 3.4.2-7. > Can you provide an swt only reproducer to ease reproducing problem? Do you mean to create some java code using the appropriate swt classes and see if that crashes after compilation and running?
(In reply to Jeremy F. Odenze from comment #2) > (In reply to Alexander Kurtakov from comment #1) > > > What is the GTK/cairo version in use? > > libcairo2 is version 1.12.2-3, libgtk2.0-0 is 2.24.10-2, libgtk-3-0 is > 3.4.2-7. > > > Can you provide an swt only reproducer to ease reproducing problem? > > Do you mean to create some java code using the appropriate swt classes and > see if that crashes after compilation and running? Yes, exactly.
(In reply to Alexander Kurtakov from comment #3) > > Do you mean to create some java code using the appropriate swt classes and > > see if that crashes after compilation and running? > > Yes, exactly. I will look into this, but don't know when to be able to report back.
I think I've found at least a workaround. I was suffering from the same problem running Eclipe Luna SR1a on a CrunchBang Linux (Waldorf) system. I noticed Eclipse was crashing sistematically whenever I tried to rename a method argument. Specifically, I could reproduce the bug this way: 1) Place the cursor above the name of an argument in the signature of some method. 2) Hit Alt+Shift+R 3) Type new name inside the textbox. 4) Hit Enter. 5) Eclipse crashes. I added this two lines in the eclipse.ini file and the problem seems disappeared: --launcher.GTK_version 2 I found this solution here: http://forums.debian.net/viewtopic.php?f=8&t=115477#p545781 This post addresses bug 430736 so I guess it could be related to this one. Moreover, the workaround seems to solve also bug 401717, which was affecting me too.
*** Bug 467041 has been marked as a duplicate of this bug. ***
This indeed seems to be related to bug 430736 which basically happens because Debian Wheezy does not have the minimum necessary version of glibc (2.14) for the GTK3 port to work, the crash log indicates presence of glic 2.13 which is outdated... If possible, please update the glibc version to 2.14 or above (see bug 430736 comment 28 for a way to do it) and run with GTK3 again.
Actually, I might have been wrong, this seems like a different crash altogether, I find only GTK3 libraries are loaded here and there is no mixup with GTK2 libraries at all. Also, the crash log from bug 467041 indicates presence of glibc 2.17.
Is this reproducible with Mars? Can you test using one of the recent Mars builds? The latest milestone build M7 can be downloaded from [1]. I investigated a bit and AFAICS this crash doesn't seem to be caused by SWT and it also doesn't seem like we can introduce a workaround in SWT for the underlying problem. The crash seems to be somewhere deeper inside GTK+ and is most probably caused by the surface that is passed to cairo_surface_set_user_data() being empty. If possible, please attach a gdb backtrace of the crash dump which might contain more details regarding how that could happen. I would also suggest reporting this bug to GTK+ at [2]. [1] http://download.eclipse.org/eclipse/downloads/drops4/S-4.5M7-201504301445/ [2] https://bugzilla.gnome.org/
Almost two years passed without reply . Closing
