Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317383 - Browser crashes if attempting to embed seamonkey 2
Summary: Browser crashes if attempting to embed seamonkey 2
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux-GTK
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 335771 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-06-20 16:02 EDT by kees1074 CLA
Modified: 2011-02-01 10:58 EST (History)
2 users (show)

See Also:


Attachments
logfile of the crash (43.18 KB, text/plain)
2010-06-20 16:04 EDT, kees1074 CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description kees1074 CLA 2010-06-20 16:02:43 EDT
Build Identifier: 20100610-0636

Running slackware 13.1. Tries eclipse version from europ until helios and also tried java 1.5 
Cannot use eclipse under slackware 

Reproducible: Always
Comment 1 kees1074 CLA 2010-06-20 16:04:19 EDT
Created attachment 172295 [details]
logfile of the crash
Comment 2 Remy Suen CLA 2010-06-20 17:00:24 EDT
What versions of Firefox/XULRunner do you have installed?
Comment 3 Grant Gayed CLA 2010-06-21 11:24:58 EDT
It looks like it's using seamonkey-2.0.4.  Can you try downloading and installing ("./xulrunner --register-user") a XULRunner on your machine?
Comment 4 kees1074 CLA 2010-06-26 04:38:15 EDT
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
Comment 5 kees1074 CLA 2010-06-26 06:16:11 EDT
(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.
Comment 6 kees1074 CLA 2010-06-26 06:21:42 EDT
(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?
Comment 7 Grant Gayed CLA 2010-06-28 09:58:55 EDT
"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.
Comment 8 Grant Gayed CLA 2010-09-16 11:37:49 EDT
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.
Comment 9 Grant Gayed CLA 2011-02-01 10:58:36 EST
*** Bug 335771 has been marked as a duplicate of this bug. ***