Community
Participate
Working Groups
Created attachment 238098 [details] hs_err_pid log I need to use Eclipse 4.2.2 J2EE because that is what allows me to use IBM worklight. However with or without the plugin, eclipse is crashing and creating hs_err_pid*log files I am attaching the log files here and other details of the machine $ java -version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) $ uname -a Linux cxps044 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux about eclipse: Eclipse Java EE IDE for Web Developers. Version: Juno Service Release 2 Build id: 20130225-0426 (c) Copyright Eclipse contributors and others 2005, 2013. All rights reserved. Visit http://www.eclipse.org/webtools
Created attachment 238099 [details] Installation details Installation details from Eclipse About
Created attachment 238100 [details] hs_err_pid log
Created attachment 238101 [details] hs err pid log
Is this frequent? Or occur in a roughly predictable scenario? I think in any case, it appears the "native code" where it occurs is related to SWT, Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z J org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(JZ)Z so will route over to them. Perhaps related to version of webkit? appears that libwebkit-1.0.so.2 is involved? Oh, just noticed from your config you are trying to use xulrunner. Have a fragment for it and everything! You might see this FAQ, which notes that sometimes "clashes" have been reported, http://www.eclipse.org/swt/faq.php#browserspecifydefault And it might help to set, in addition to xulrunners's path, if I'm reading it right, the property -Dorg.eclipse.swt.browser.DefaultType=mozilla But, I'm sure SWT team can give better advise ... I'm half guessing.
Yes setting the value -Dorg.eclipse.swt.browser.DefaultType=mozilla at the end of the eclipse.ini and restarting eclipse works around the problem, thanks for comment 4. I was getting a crash whenever I clicked on an .html file, so this was probably related to rendering. However sometimes this happened immediately on startup, perhaps some rendering was involved even then. I'll observe eclipse with this change throughout the day and update if there are any issues faced even after this workaround Thanks again
(In reply to David Williams from comment #4) > Oh, just noticed from your config you are trying to use xulrunner. Have a > fragment for it and everything! > You might see this FAQ, which notes that sometimes "clashes" have been > reported, > http://www.eclipse.org/swt/faq.php#browserspecifydefault > And it might help to set, in addition to xulrunners's path, if I'm reading > it right, the property > > -Dorg.eclipse.swt.browser.DefaultType=mozilla > > But, I'm sure SWT team can give better advise ... I'm half guessing. Thanks for jumping on this David :) This does seem to be a case of mixing up of xulrunner and webkit libraries causing the crash. The DefaultType flag suggested above should avoid loading of webkit libraries and resolve the crash. Please close the bug if you don't see the crash anymore. Thanks!
(In reply to Arun Thondapu from comment #6) > (In reply to David Williams from comment #4) > > Oh, just noticed from your config you are trying to use xulrunner. Have a > > fragment for it and everything! > > You might see this FAQ, which notes that sometimes "clashes" have been > > reported, > > http://www.eclipse.org/swt/faq.php#browserspecifydefault > > And it might help to set, in addition to xulrunners's path, if I'm reading > > it right, the property > > > > -Dorg.eclipse.swt.browser.DefaultType=mozilla > > > > But, I'm sure SWT team can give better advise ... I'm half guessing. > > Thanks for jumping on this David :) > This does seem to be a case of mixing up of xulrunner and webkit libraries > causing the crash. The DefaultType flag suggested above should avoid loading > of webkit libraries and resolve the crash. > > Please close the bug if you don't see the crash anymore. Thanks! I'm assuming the crash is resolved and will go ahead and close the bug. Please re-open if that is not the case...
