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 http://myspeed.visualware.com/index.html (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: http://crash-stats.mozilla.com/report/index/13ec81d5-0644-4db2-85b6-553812090426 http://crash-stats.mozilla.com/report/index/62ab84ea-480c-490c-855b-f4edc2090426 http://crash-stats.mozilla.com/report/index/c0c11e02-6c5d-434e-8c41-7a8da2090426 http://crash-stats.mozilla.com/report/index/fde9827a-8998-493a-a3a6-42df22090426
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
Product: SeaMonkey → Core
QA Contact: general → java.oji
Version: unspecified → 1.9.1 Branch
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.
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.
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
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.