Community
Participate
Working Groups
Created attachment 109896 [details] Error log for the crash Build ID: I20080617-2000 Steps To Reproduce: 1. Create new dynamic web project, target GlassFish 2. Create index.jsp 3. Run as > Run on server (GlassFish) 4. Eclipse crashes Java HotSpot VM completely More information: I'm using Eclipse 3.4 on Ubuntu 7.04 32bit linux. Everything has been working fine for a while, until my project started crashing whenever I'd run it on my GlassFish server (running locally). The specific SIGSEGV I get using -consoleLog is: # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x8212fc08, pid=7790, tid=3085211312 # # Java VM: Java HotSpot(TM) Client VM (11.0-b15 mixed mode linux-x86) # Problematic frame: # C [libgklayout.so+0x122c08] # # An error report file with more information is saved as: # /home/sam/hs_err_pidxxxx.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. # The fault is always with this module, and I have used 3 different JDKs to make the same problem pop up (1.6_03, _07, and the newest release candidate). I tried using different fixes outlined in the other bug threads without, but this seems fundamentally different to me as it's happening "Outside the JVM in native code). Eclipse would also crash for me before this bug popped up immediately following startup, with a SIGSEGV in the same libgtklayout frame, but that stopped once I reinstalled Eclipse and specified my JDK location properly.
(In reply to comment #0) > Created an attachment (id=109896) [details] > Error log for the crash > > Build ID: I20080617-2000 > > Steps To Reproduce: > 1. Create new dynamic web project, target GlassFish > 2. Create index.jsp > 3. Run as > Run on server (GlassFish) > 4. Eclipse crashes Java HotSpot VM completely > > > More information: > I'm using Eclipse 3.4 on Ubuntu 7.04 32bit linux. Everything has been working > fine for a while, until my project started crashing whenever I'd run it on my > GlassFish server (running locally). > > The specific SIGSEGV I get using -consoleLog is: > # > # An unexpected error has been detected by Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x8212fc08, pid=7790, tid=3085211312 > # > # Java VM: Java HotSpot(TM) Client VM (11.0-b15 mixed mode linux-x86) > # Problematic frame: > # C [libgklayout.so+0x122c08] > # > # An error report file with more information is saved as: > # /home/sam/hs_err_pidxxxx.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. > # > > The fault is always with this module, and I have used 3 different JDKs to make > the same problem pop up (1.6_03, _07, and the newest release candidate). > > I tried using different fixes outlined in the other bug threads without, but > this seems fundamentally different to me as it's happening "Outside the JVM in > native code). > > Eclipse would also crash for me before this bug popped up immediately following > startup, with a SIGSEGV in the same libgtklayout frame, but that stopped once I > reinstalled Eclipse and specified my JDK location properly. > Interestingly, I also get the occasional crash when just editing a file, but it's the same module in the SIGSEGV: libgklayout.so+0x122c08, so perhaps it is a problem with that code? It also deploys to the GlassFish server fine, crashing after that process is completed, so it's probably a GUI issue of some sort.
(In reply to comment #1) > (In reply to comment #0) > > Created an attachment (id=109896) [details] [details] > > Error log for the crash > > > > Build ID: I20080617-2000 > > > > Steps To Reproduce: > > 1. Create new dynamic web project, target GlassFish > > 2. Create index.jsp > > 3. Run as > Run on server (GlassFish) > > 4. Eclipse crashes Java HotSpot VM completely > > > > > > More information: > > I'm using Eclipse 3.4 on Ubuntu 7.04 32bit linux. Everything has been working > > fine for a while, until my project started crashing whenever I'd run it on my > > GlassFish server (running locally). > > > > The specific SIGSEGV I get using -consoleLog is: > > # > > # An unexpected error has been detected by Java Runtime Environment: > > # > > # SIGSEGV (0xb) at pc=0x8212fc08, pid=7790, tid=3085211312 > > # > > # Java VM: Java HotSpot(TM) Client VM (11.0-b15 mixed mode linux-x86) > > # Problematic frame: > > # C [libgklayout.so+0x122c08] > > # > > # An error report file with more information is saved as: > > # /home/sam/hs_err_pidxxxx.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. > > # > > > > The fault is always with this module, and I have used 3 different JDKs to make > > the same problem pop up (1.6_03, _07, and the newest release candidate). > > > > I tried using different fixes outlined in the other bug threads without, but > > this seems fundamentally different to me as it's happening "Outside the JVM in > > native code). > > > > Eclipse would also crash for me before this bug popped up immediately following > > startup, with a SIGSEGV in the same libgtklayout frame, but that stopped once I > > reinstalled Eclipse and specified my JDK location properly. > > > > Interestingly, I also get the occasional crash when just editing a file, but > it's the same module in the SIGSEGV: libgklayout.so+0x122c08, so perhaps it is > a problem with that code? > > It also deploys to the GlassFish server fine, crashing after that process is > completed, so it's probably a GUI issue of some sort. > Alright, more thorough investigation reveals that the problem only occurs when using the internal eclipse browser to view the program display. I've downgraded the priority, but the bug reliably happens when publishing a dynamic web project, using the internal web browser to view it, so it's probably still a good idea to look into it. In my case, other, less reproducible crashes result in the same SIGSEGV, so I'm not exactly sure what the heck is going on.
> using the internal web browser to view it Can you please get Eclipse 3.5 M1 and see whether the problem has gone away? We've fixed some crashes in that release and our browser guy isn't around at the moment.
(In reply to comment #3) > > using the internal web browser to view it > > Can you please get Eclipse 3.5 M1 and see whether the problem has gone away? > We've fixed some crashes in that release and our browser guy isn't around at > the moment. > I'll do that when I get back to work next week. I don't think it's an issue only with the internal browser though - Eclipse crashes the JVM sometimes when editing code, with the same libgtklayout.so frame error.
(In reply to comment #0) > Created an attachment (id=109896) [details] > Error log for the crash > > Build ID: I20080617-2000 > > Steps To Reproduce: > 1. Create new dynamic web project, target GlassFish > 2. Create index.jsp > 3. Run as > Run on server (GlassFish) > 4. Eclipse crashes Java HotSpot VM completely > > > More information: > I'm using Eclipse 3.4 on Ubuntu 7.04 32bit linux. Everything has been working > fine for a while, until my project started crashing whenever I'd run it on my > GlassFish server (running locally). > > The specific SIGSEGV I get using -consoleLog is: > # > # An unexpected error has been detected by Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x8212fc08, pid=7790, tid=3085211312 > # > # Java VM: Java HotSpot(TM) Client VM (11.0-b15 mixed mode linux-x86) > # Problematic frame: > # C [libgklayout.so+0x122c08] > # > # An error report file with more information is saved as: > # /home/sam/hs_err_pidxxxx.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. > # > > The fault is always with this module, and I have used 3 different JDKs to make > the same problem pop up (1.6_03, _07, and the newest release candidate). > > I tried using different fixes outlined in the other bug threads without, but > this seems fundamentally different to me as it's happening "Outside the JVM in > native code). > > Eclipse would also crash for me before this bug popped up immediately following > startup, with a SIGSEGV in the same libgtklayout frame, but that stopped once I > reinstalled Eclipse and specified my JDK location properly. > Alright, what 3.5 M1 package would be best for testing a Java EE project? I downloaded the Eclipse SDK and it didn't seem to have the features I needed to test my project (JSP code editor, server interfaces, etc). Thanks
Can you try copying the two swt jars from the 3.5M1 plugins directory into your 3.4's plugins directory (and don't forget to remove the swt 3.4 jars)? I think this will work, unless some plug-ins have their swt dependencies == v3.4 instead of >= v3.4.
(In reply to comment #6) > Can you try copying the two swt jars from the 3.5M1 plugins directory into your > 3.4's plugins directory (and don't forget to remove the swt 3.4 jars)? I think > this will work, unless some plug-ins have their swt dependencies == v3.4 > instead of >= v3.4. > Eclipse will not start up after replacing the two swt jars. Would you like me to post the error message, or is there another way to go about this?
Please do.
Created attachment 110970 [details] Output from eclipse -consoleLog
Created attachment 110971 [details] log file generated by eclipse
(In reply to comment #8) > Please do. > Alright, I've attached the relevant log files. consoleLog is the output from eclipse -consoleLog, and the other file is the log file generated from eclipse. Thanks.
Grant, any ideas?
The following should work: - take your original 3.4-based product (so with swt's 3.4-shipped jars) - launch it with line: ./eclipse -vmargs -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null - retrieve SWT from HEAD into your workspace: http://www.eclipse.org/swt/cvs.php - as a bonus, insert as the first line of method Mozilla.create(Composite,int): org.eclipse.swt.graphics.Device.DEBUG = true; - invoke Run > Run Configurations... - create a new "Eclipse Application" run configuration, press the Run button - this will bring up a 3.4-based eclipse instance with the SWT from your workspace, so try your case(s) in this instance - if it still fails then please follow up here with the mozilla/xulrunner path that's written to stdout when the first Browser instance is created
Timed out, closing report. Please reopen if you still see this problem when self-hosting as described in comment 13.
