Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315588 - Eclipse crashed under ubuntu 9.10 when using buid in browser
Summary: Eclipse crashed under ubuntu 9.10 when using buid in browser
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 critical with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Grant Gayed CLA
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2010-06-03 09:48 EDT by Max Areshkau CLA
Modified: 2014-02-13 09:01 EST (History)
7 users (show)

See Also:


Attachments
Eclipse crash log (78.76 KB, text/x-log)
2010-06-03 09:54 EDT, Max Areshkau CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Max Areshkau CLA 2010-06-03 09:48:30 EDT
Build Identifier: I20100527-1700

Eclipse crashes under ubuntu when I am using build in browser. I have read that it's crashed becouse XR 1.9.1. I have provided XR 1.9.2 for it and it contunue crahs, but with other exception. Eclipse 3.5.2 works well for me.

Reproducible: Always

Steps to Reproduce:
1.It s reproduceble when I run tests for my component.
2.See a bug https://jira.jboss.org/browse/JBIDE-6373
3.
Comment 1 Max Areshkau CLA 2010-06-03 09:54:47 EDT
Created attachment 170955 [details]
Eclipse crash log
Comment 2 Felipe Heidrich CLA 2010-06-03 09:59:58 EDT
Grant, do yo know what is this ?
I didn't see SWT in the stacktrace...
Comment 3 Andrew Overholt CLA 2010-06-03 10:03:58 EDT
Is this using the XPCOM Java stuff?
Comment 4 Max Areshkau CLA 2010-06-03 10:06:57 EDT
Yes, it's used xpcom. I am usign xulrunner 1.9.2 release from mozilla repository for linux x86.
Comment 5 Grant Gayed CLA 2010-06-03 10:26:00 EDT
The attached dump does not reveal much beyond JavaXPCOM finalizing some object.  Are you able to provide an swt-only repeatable case of this?  If not, since you said that this worked in 3.5.2, you could help on your end by determining which eclipse 3.6 milestone release had the change that introduced the problem.  These are available at http://archive.eclipse.org/eclipse/downloads/index.php , under the currently mislabeled section "Archived 3.5 Stream Stable Builds".
Comment 6 Max Areshkau CLA 2010-06-07 02:10:08 EDT
I have checked on which version the issue reproducible. It works fine on Milestone 4 and crashes on milestone 5 (Build id: I20100129-1300).
Comment 7 Grant Gayed CLA 2010-06-08 11:29:31 EDT
Thanks for determining this.  Comparing these versions, the changes are not what I would have expected to introduce a problem like you're seeing.  Can you try one more experiment?

- run your eclipse 3.6M4
- connect to CVS ( http://www.eclipse.org/swt/cvs.php )
- retrieve the org.eclipse.swt and org.eclipse.swt.gtk.linux.x86 projects with version v3624, and rename org.eclipse.swt's .classpath_gtk to .classpath
- self-host (Run > Run As... > Eclipse Application), run your tests in this self-hosted eclipse instance, and they should be fine, close this self-hosted eclipse
- select the Mozilla.java class, right-click > Team > Show History
- the History view shows that revision 1.152 is loaded
- choose revision 1.153, right-click -> Get Contents
- self-host, run your tests in this self-hosted eclipse instance, are they ok?
- if this did not show the problem then Get the contents of Mozilla.java's revision 1.154, and the tests should now show the problem
- which revision (1.153 or 1.154) made the problem appear for you?
Comment 8 Max Areshkau CLA 2010-06-09 08:26:34 EDT
It's works on 1.153 and begin crashes on 1.154.
So problem appear on 1.154 version.
Comment 9 Grant Gayed CLA 2010-06-14 14:38:22 EDT
The changes between these revisions are updates to adapt to changes in XULRunner 1.9.2.  I notice that you're using xulrunner-1.9.2, so I suspect that the change that's causing your problem is not in this revision, but this revision enables the code path with the problematic change to run.  Do you still have your workspace with SWT v3624 + Mozilla rev. 1.154 available?  If so, near the top of its execute() method can you change:

if (!IsPre_1_9) {

to:

if (false && !IsPre_1_9) {

I think that this will make your test stop crashing.
Comment 10 Max Areshkau CLA 2010-06-15 04:09:10 EDT
Yes, adding false to if make stop crashing of test.
Comment 11 Max Areshkau CLA 2010-06-15 04:47:36 EDT
This issue reproducible under Windows too.
Comment 12 Alexander Kurtakov CLA 2013-12-20 04:49:24 EST
Is this problem still reproducible in Kepler (4.3)?
Comment 13 Alexander Kurtakov CLA 2014-02-13 09:01:07 EST
More than a month without reply from submitter(s). Issue is not reproducible with supported swt version on my side. Closing.
Please reopen if you still experience the issue with swt 4.3 or newer.