Created attachment 274179 [details] detailed java error log Both eclipse 3.5 (stable in portage) and 3.6 (from layman/dustin overlay) crashes when tooltip appears. here is the error: $ eclipse-3.6 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x8d2fd260, pid=4715, tid=3063405424 # # JRE version: 6.0_24-b07 # Java VM: Java HotSpot(TM) Server VM (19.1-b02 mixed mode linux-x86 ) # Problematic frame: # C [libmozjs.so+0x76260] # # An error report file with more information is saved as: # /home/nardi/hs_err_pid4715.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # File libmozjs.so belongs to dev-lang/spidermonkey so it's probably javascript issue. I figured out, that reemerging with USE="-xulrunner" fixed this. I'd suggest eclipse-sdk[xulrunner] to be masked.
Please post your `emerge --info' output too.
Created attachment 274653 [details] emerge --info
I have the same issue. It is also described here http://gentoowar.blogspot.com/2011/04/new-xulrunner-and-eclipse.html and here http://www.niftiestsoftware.com/2011/02/26/eclipse-crashing-on-documentation-popups-appearing/. But both suggestions did not resolve the crash for me. :( The only thing that has helped so far was an "emerge -C xulrunner" making it impossible to use firefox.
I have the same issue. A simple workaround is to create empty libmozjs.so in the working directory and start eclipse from there. It works for me
This worked for me as a workaround: add this to /etc/portage/package.use dev-java/swt -xulrunner unmerge swt and then reinstall eclipse: # emerge -C =dev-java/swt-1.5.2 # emerge dev-util/eclipse-sdk-3.5.1-r1
I can confirm this issue and also that disabling the xulrunner flag for swt fixes it. Any news on this?
Closing as these versions are ancient and the package has been removed from the tree. xulrunner is long dead now so if the package were to return, I doubt this would be an issue.