Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1.Open internal browser view 2.browser around google search results for about couple of minutes 3.An unexpected error has been detected by Java Runtime Environment: More information: the bug is from eclipse-rcp-europa-fall2-linux-gtk.tar and using jdk1.6.0_03 on i386 GNU/Linux hs_err_pid9986.log is generated when eclipse aborts.
>hs_err_pid9986.log is generated when eclipse aborts. Please attach this here.
Created attachment 90539 [details] the error log generated when my eclipse aborted The error log is attached. Thanks
The GRE libraries are from seamonkey-1.0.5. Can you confirm: - You should have a file on your machine like /etc/gre.conf or /etc/gre.d/gre.conf. What is in it? - Do you still see this problem with the eclipse 3.4M5 milestone ( http://download.eclipse.org/eclipse/downloads/drops/S-3.4M5-200802071530/index.php )? I ask because until this release there were some assumptions made in the Browser that a detected 1.8-level GRE would be xulrunner or firefox (seamonkey, which is the other 1.8-level variant, is not as common).
For me, this bug is a blocker. When starting eclipse with a new workspace, the internal browser is used to display the start page, making eclipse crash. Also, when the code-completion drop-down is shown in the editor, I guess it uses HTML, because that, too, crashes eclipse. It makes eclipse unusable. I hope this is the same bug - at least, when starting with an old workspace, I acutally have to go to window -> show view (or something) -> other -> general -> internal browser to generate the crash, or simply input something like System.out.[ctrl+space] to open the code-completion window, which also crashes eclipse. All this also happens when running eclipse with -clean. My own configuration in ~/.eclipse has been backed up and removed from that location, so the configuration is clean too. This happens with the official build and also with the gentoo portage variety. ALSO happens with the version 3.5M5 on the link supplied below. eclipse says this: # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x82074b4a, pid=25670, tid=3085003664 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode) # Problematic frame: # C [libmozjs.so+0x1bb4a] # # An error report file with more information is saved as hs_err_pid25670.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # crash message says: JVM terminated. Exit code=1 /usr/bin/java -Xms128m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Djava.library.path=/usr/lib -jar /usr/lib/eclipse-3.3/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar -os linux -ws gtk -arch x86 -showsplash -launcher /usr/lib/eclipse-3.3/eclipse -name Eclipse --launcher.library /usr/lib/eclipse-3.3/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.2.R331_v20071019/eclipse_1021.so -startup /usr/lib/eclipse-3.3/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar -exitdata 688008 -vm /usr/bin/java -vmargs -Xms128m -Xmx512m -XX:PermSize=64m -XX:MaxPermSize=256m -Djava.library.path=/usr/lib -jar /usr/lib/eclipse-3.3/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
re: comment 4 I don't think you're seeing the same problem, because your problematic C frame is different and you see the crash at the first time the Browser is created (comment 0 indicates that the crash for this report happens later). Please open a new report and include your hs_err_pid25670.log .
I'm seeing a bug fitting this description, but no logs are generated. Steps to reproduce: 1. Open internal browser 2. Open http://standingcloud.com 3. Eclipse crashes. No error, no warning, no log (AFAIK) I'm running: Eclipse JEE x86_64 Version: Indigo Service Release 1 Build id: 20110916-0149
FYI: I tried changing the affected Eclipse version to 3.7.1 since I'm seeing this on a fresh install of Indigo. I don't have permission on this bug report to do so. Also, since the browser component seems tied to the OS, (and which version of Mozilla is supplied to the OS) .... I am encountering this on: Ubuntu 11.10 Oneiric Mozilla Firefox 7.0.1
Is this bug still relevant?
Well, it most likely still exists... however I am currently no longer using Eclipse, and hence do not use it's internal browser anymore. So it is therefore no longer a relevant bug to me. If it affects someone else, and still exists in current versions of Eclipse, then it will be relevant to them.
