Community
Participate
Working Groups
Created attachment 244691 [details] Java dump from crash Installed Eclipse 4.4 on Linux Mint. Selected 'Eclipse Marketplace' from the 'Help' menu. Eclipse crashed while loading the popup window. This is _not_ an intermittent fault. It happens every time. This may be related to Bug 419729, in that it appears to be related to GTK 3. If I do the following before running Eclipse, the problem does not occur: export SWT_GTK3=0 Am using Linux Mint 16 (Petra) MATE, 64-bit. I believe Mint is Ubunutu-based. Have attached one of the error logs from the crash.
Hi, from the logs it seems both GTK2 and GTK3 got loaded. Can you provide the output of the command ldd on libswt-pi-gtk-4427.so and libswt-pi3-gtk-4427.so? These are there in the plugin fragment org.eclipse.swt.gtk.linux.x86_64_3.103.0.v20140605-2012.jar. you can see this in the plugins folder. if the eclipse started once you can find these files eclipse/configuration/org.eclipse.osgi/398/0/.cp Thanks Sravan
Created attachment 244717 [details] Output of: ldd -v libswt-pi3-gtk-4427.so Output of: ldd -v libswt-pi3-gtk-4427.so
Created attachment 244718 [details] Output of: ldd -v libswt-pi-gtk-4427.so Output of: ldd -v libswt-pi-gtk-4427.so
Hi, I find couple of issues in my analysis based on the logs provided. 1. Awt is used by the marketplace client. We have a known bug 431330 where if LaF for AWT is GTK GTK2 will get loaded. since eclipse loads GTK3 by default this causes a crash. The solution is to use gtk2 for eclipse or rework the code for marketplace to use Laf to other than GTK 2. The second issue I have here is loading of wayland libraries. eclipse does not support wayland yet. so I feel there might be a problem here. Thanks Sravan
I had this problem using jre 1.8.0_11 on Ubuntu 12.04 64-bit. Either reverting to jre 1.7.0_65, or SWT_GTK3=0 fixed it.
Created attachment 247526 [details] Crash on Kubuntu 14.4 TLS with JDK 1.7
Hi Sorry if I did the wrong thing but this is the first time I report a bug on eclipse ( not sure should I create a new issue or not ... ) Actually I'm also facing a crash when starting the marketplace from a fresh install of eclipse Luna. I'm using Luna Service Release 1 (4.4.1) Build id: 20140925-1800 on a Kubuntu 14.04 LTS with a JDK 1.7.0_67-b01. The ide crashes as soon as I start the marketplace from the menu. I've attaches the log as ( Crash on Kubuntu 14.4 TLS with JDK 1.7). Any ideas ?
Same issue--different distribution. Arch Linux Eclipse 4.4.1 Java 1.8.0_20
Any updates on this bug? Eclipse is intermittently crashing every 3-4 minutes. But will instantly crash when visiting Marketplace. Any workarounds? The "export SWT_GTK3=0" workaround didn't work in ArchLinux.
(In reply to Saad Malik from comment #9) > But will instantly crash when visiting Marketplace. Sravan or Arun, can you use this information to reproduce the problem?
(In reply to Dani Megert from comment #10) > (In reply to Saad Malik from comment #9) > > But will instantly crash when visiting Marketplace. > > Sravan or Arun, can you use this information to reproduce the problem? We already know what the problem here is and the workaround is mentioned in comment 4. Please use an AWT LnF other than GTK+ to avoid this crash. In the case of OpenJDK, it used to load GTK+ 2 even when AWT LnF is different from GTK+ but I think that bug is fixed in the newer releases as per bug 431330 comment 11. If you need to use the GTK+ LnF for AWT, then the only alternative is to use eclipse with GTK+ 2 (either via SWT_GTK3=0 or via adding the --launcher.GTK_version parameter in eclipse.ini)
(In reply to Arun Thondapu from comment #11) > (In reply to Dani Megert from comment #10) > > (In reply to Saad Malik from comment #9) > > > But will instantly crash when visiting Marketplace. > > > > Sravan or Arun, can you use this information to reproduce the problem? > > We already know what the problem here is and the workaround is mentioned in > comment 4. Indeed.
*** Bug 429209 has been marked as a duplicate of this bug. ***
*** Bug 445294 has been marked as a duplicate of this bug. ***
@Arun Both of the following workaround didn't work for me: 1) export SWT_GTK3=0 2) Setting Appearance to Classic/Dark (I tried all permutations). As soon as I visit the marketplace, Eclipse crashes. I'll do some more debugging/strace later tonight.
Eclipse Market Place uses awt in the code there are two places it is used 1. Image manipulation in org.eclipse.epp.internal.mpc.ui.util.Util class and 2. Sending email in org.eclipse.epp.internal.mpc.ui.wizards.ShareSolutionLink class. Awt loads GTK2. and eclipse by default starts in GTK3. GTK2 and GTK3 cannot be loaded in the same process. That is the reason you are seeing this crash. the workaround is to use GTK2 for eclipse as well. This can be achieved in the following ways 1. add the following lines to eclipse.ini before -vmargs(recommended approach) --launcher.GTK_version 2 2. set the environment variable SWT_GTK3 to 0 before launching eclipse. you need to do this every time you launch eclipse
@Sravan Neither of those two workarounds worked on ArchLinux. The only workaround that worked was changing the SWT provider to Mozilla: Append "-Dorg.eclipse.swt.browser.DefaultType=mozilla" after the "-vmargs" line in /usr/share/eclipse/eclipse.ini.
Is there a sane and safe way for me to check in the Marketplace Client whether it's safe to use AWT? Or do I have to pull the really big plug of disabling it completely for Linux with GTK3 enabled. And how do I properly check for GTK3 use in Eclipse?
I'm moving this bug now to the marketplace client because the only way marketplace client can be used when Eclipse is running with GTK+ 3 is by removing the dependency on AWT as the AWT code causes GTK+ 2 to be loaded by the Eclipse process. The only valid workaround to be able to use MPC from Eclipse right now is to force Eclipse also to use GTK+ 2 via the steps mentioned in comment 16. @Saad The crash you're referring to is probably bug 428347 (or similar) which is not really specific to marketplace client but could happen wherever a browser widget is used, are you able to use the internal web browser in eclipse? Please open a separate bug and provide the crash logs if you think its not bug 428347.
(In reply to Carsten Reckord from comment #18) > Is there a sane and safe way for me to check in the Marketplace Client > whether it's safe to use AWT? > > Or do I have to pull the really big plug of disabling it completely for > Linux with GTK3 enabled. And how do I properly check for GTK3 use in Eclipse? AWT definitely cannot be used when Eclipse is running with GTK+ 3.x. You could use the Java property "org.eclipse.swt.internal.gtk.version" which is set by SWT for finding the exact GTK+ version being used by Eclipse...
*** Bug 453089 has been marked as a duplicate of this bug. ***
*** Bug 438328 has been marked as a duplicate of this bug. ***
I have published a preliminary fix that avoids using AWT on Linux in our nightly builds[1]. I'd like to push out a release with the fix as soon I've done some more testing, but my Linux testing vm is currently broken and the other boxes around that have UI are all still on GTK2. I'll hopefully get around to some proper testing early next week, but I'd like to invite everybody to try the fix from the nightly. If you do, please also try the share as mail action (little arrow on the entry, then "Email"). What to expect: - Scaled images (e.g. solution icons) should still look fine. I managed to remove the image scaling AWT code without getting the bad results that originally made me use AWT. - Email action might not work with Linux (bug 384840). I'll look into that further. [1] http://download.eclipse.org/mpc/nightly
Arun, thank you for helping with all the SWT details. Not directly related, but while I have your ear ;) ... Do you know if I should expect similar compatibility issues wrt SWT browser support? Or does the internal browser detection magic already guard against mixing GTK versions? In MPC, we are using both the SWT Browser widget directly, and the embedded browser editor through IWorkbenchBrowserSupport.
Fixed in http://git.eclipse.org/c/mpc/org.eclipse.epp.mpc.git/commit/?id=a7f4d411d70c0525b562c77d9ae5ac76bdc23e40. The fix will be available in Luna SR2, starting with the upcoming RC1, and in the next Mars milestones. I'm still not sure if we could run into similar problems with our use of the embedded browser widget. But that's a separate issue anyway, and aside from having a couple of extra hoops to jump through to get any browser in a GTK3 eclipse, I didn't manage to get it to crash so far...
