Crashing 20090426 nightly



Core Graveyard
Java: OJI
9 years ago
6 years ago


(Reporter: NoOp, Unassigned)



1.9.1 Branch

Firefox Tracking Flags

(Not tracked)





9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b5pre) Gecko/20090425 SeaMonkey/2.0b1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b5pre) Gecko/20090426 SeaMonkey/2.0b1pre

Upgraded from Gecko/20090425 SeaMonkey/2.0b1pre to Gecko/20090426 SeaMonkey/2.0b1pre - with existing Java window open. Upon attempt to restore SM crashes. Crash reports included.

Reproducible: Always

Steps to Reproduce:
1. Gecko/20090425 SeaMonkey/2.0b1pre with browser window open to (Java based speed test).
2. Upgrade to Gecko/20090426 SeaMonkey/2.0b1pre (leave java window open.
3. Following Gecko/20090426 SeaMonkey/2.0b1pre upgrade, click restart to install the update.
Actual Results:  
Upon restart SeaMonkey crashes every time.

Expected Results:  
Should not crash, but instead restore sessions.

Related crash reports:

Comment 1

9 years ago
so, sun's plugin is crashing you. please file a bug against sun, feel free to reference this bug there, and please provide your bugparade url here.
Severity: normal → critical
Component: General → Java: OJI
Keywords: crash
Product: SeaMonkey → Core
QA Contact: general → java.oji
Version: unspecified → 1.9.1 Branch

Comment 2

9 years ago
Can do. However, the crash only occurs w/20090426 - java (and the speed test applet) is working just fine in 20090425. So I wonder if this is solely a Sun plugin issue.

Comment 3

9 years ago
it might be, it might not be. however, their plugin is not yet open source, so we can't easily do much w/o their help. if they need us, they know where to find us.


8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard

Comment 4

6 years ago
OJI has been discontinued and Java now runs out-of-process, so this stuff has probably changed a lot. This bug has no info about current software versions, please file a new bug for new issues or reopen this one with current info, including a crash signature if it still happens and move it to a component outside of graveyard.
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE

Comment 5

6 years ago
Agree. I can no longer replicate. Thanks for the clean-up.
You need to log in before you can comment on or make changes to this bug.