Closed
Bug 56509
Opened 24 years ago
Closed 24 years ago
Java plugin install segfaults
Categories
(SeaMonkey :: Installer, defect, P3)
Tracking
(Not tracked)
People
(Reporter: chrisf, Assigned: ssu0262)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.17 i686) BuildID: 2000101015 When attempting to install the java plugin, mozilla segfaults. Curiously, this occurs before the plugin download normally, but with strace, it occurs after the download. Reproducible: Always Steps to Reproduce: Visit any Java site, follow plugin install steps as prompted Actual Results: mozilla segfault Expected Results: installed plugin Here's the tail of the strace: Document http://home.netscape.com/plugins/jvm.html loaded successfully we don't handle eBorderStyle_close yet... please fix me Adding element 0 : _blank we don't handle eBorderStyle_close yet... please fix me 2 Adding Progress element 0 : _blank clearing PRIMARY clipboard Setting content window *** Pulling out the charset in SetSecurityButton JavaScript error: line 0: uncaught exception: [Exception... "Failure" code: "-2147467259" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "http://home.netscape.com/plugins/jvm.html Line: 33"] Gdk-CRITICAL **: file gdkwindow.c: line 716 (gdk_window_ref): assertion `window != NULL' failed.
Comment 1•24 years ago
|
||
I can confirm almost the same result with M18, except for that mozilla won't segfault. the JavaScript error occurs tough, and also in JavaScript Console. Latest build (Build ID: 2000101521) gives different result: JavaScript error: line 33: missing } in compund statement This appears to be a different bug however, as it's generally triggered by entering data in this box.
Comment 2•24 years ago
|
||
this is bug 55537 *** This bug has been marked as a duplicate of 55537 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
Component: Installer: XPI Packages → Installer
QA Contact: agracebush → general
You need to log in
before you can comment on or make changes to this bug.
Description
•