| Summary: | Browser crashes if attempting to embed seamonkey 2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | kees1074 | ||||
| Component: | SWT | Assignee: | Grant Gayed <grant_gayed> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | nickkolegraff, remy.suen | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
kees1074
Created attachment 172295 [details]
logfile of the crash
What versions of Firefox/XULRunner do you have installed? It looks like it's using seamonkey-2.0.4. Can you try downloading and installing ("./xulrunner --register-user") a XULRunner on your machine?
The aboutbox of firefox gives the following information: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (In reply to comment #3) > It looks like it's using seamonkey-2.0.4. Can you try downloading and > installing ("./xulrunner --register-user") a XULRunner on your machine? I build and installed xulrunner (version: 1.9.2). typed : xulrunner --register-user No response returns to the prompt. (In reply to comment #5) > (In reply to comment #3) > > It looks like it's using seamonkey-2.0.4. Can you try downloading and > > installing ("./xulrunner --register-user") a XULRunner on your machine? > > I build and installed xulrunner (version: 1.9.2). > > typed : xulrunner --register-user > > No response returns to the prompt. Started eclipse. Now eclipse does not crash. What has happened? "xulrunner --register-user" registered the download xulrunner as an available Gecko renderer on your machine, so the Browser control is now finding it and using it instead of seamonkey. Downgrading importance since a workaround exists. It's strange that your linux distro does not ship a registered xulrunner already, as most of them do. I'll have to download a seamonkey like what you have and see why it's crashing. The failed call is NS_NewLocalFile, which is just a straight C call, and is probably the first call being made to seamonkey. I wonder if seamonkey is no longer embeddable for some reason. I've confirmed that the Browser successfully embeds seamonkey versions < 2, but that seamonkey 2 no longer works. Updating report title accordingly. Embedding of seamonkey is not an expected use case for the Browser. Some effort was previously made to make this case work for the benefit of some linux distros that shipped ~ 4 years ago with a seamonkey as their only embeddable gecko (so no xulrunner, which was just newly released). However linux distros today should at least have a xulrunner for the Browser to use, if not WebKitGTK, and there are no plans to try to support seamonkey versions >= 2. It's quite unusual that Slackware includes neither of these. Coincidentally this crash will actually become fixed when the fix for bug 319123 is released, as it will limit the seamonkey versions that the eclipse launcher will consider for the Browser to use to versions < 2. In such cases Browser functionality will simply be disabled, but no crash will occur. Closing as WONTFIX. *** Bug 335771 has been marked as a duplicate of this bug. *** |