Community
Participate
Working Groups
Created attachment 223182 [details] JVM coredump file Using fedora core 17 64-bit Linux on Intel with latest upgrades from Fedora, following happens. 1.) Fire up eclipse IDE, works fine. 2.) Open an interface I started coding. 3.) Type "public IEzs" starting a method declaration. 4.) At this point, hit Ctrl-Space, since I have some interfaces in the workspace that begin with "IEzs" and I want to pop-up that suggests them. 5.) The pop-up shows up with the correct suggestions, however UI at this point is locked. 6.) Whole thing crashes and dissapears a little bit later. I rebooted the Linux box just to see if there is some dangling resources somewhere, didn't help. Note that this eclipse installation worked just fine for months. I suspect this happened after I downloaded some new patches for Fedora core 17 distribution.
Hooray, I found a workaround. This is related to the browser support and the xulrunner issue, bug 333444. I added following 2 lines to the eclipse.ini, and then it works fine: -Dorg.eclipse.swt.browser.XULRunnerPath==/usr/lib64/xulrunner/ -Dorg.eclipse.swt.browser.UseWebKitGTK=true So I'm all set, but it would be really nice if IDE was able to somehow autodetect this issue.
(In reply to comment #1) > Hooray, I found a workaround. This is related to the browser support and the > xulrunner issue, bug 333444. Eclipse/SWT 3.7.x should have defaulted to using WebKitGTK in the first place (-Dorg.eclipse.swt.browser.UseWebKitGTK=true should not be needed). With your workaround in place, can you try opening Eclipse's Internal Web Browser view and verify that you're successfully able to navigate anywhere? Also, can you see if your /usr/lib64 directory contains a libwebkitgtk-1.0.so.0 link to a similarly-named lib? Or does it only have a link like libwebkitgtk-3.0.so.0?
One other question: Are you just running a plain Eclipse download, or does it have additional plug-ins (eg.- C++ dev tools, etc.)?
Timed out, closing report. I'm assuming that the GTK2 WebKitGTK+ package is not installed, which I think this is the case by default on Fedora 17. This would explain why the Browser did not attempt to embed WebKitGTK+.