Site crashes SeaMonkey

RESOLVED INCOMPLETE

Status

SeaMonkey
General
--
critical
RESOLVED INCOMPLETE
5 years ago
5 years ago

People

(Reporter: willprot, Unassigned)

Tracking

({crash, stackwanted})

SeaMonkey 2.12 Branch
x86
Windows XP
crash, stackwanted

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Navigating to any forum page of battlelog.battlefield.com with JavaScript turned ON such as http://battlelog.battlefield.com/bf3/forum/view/2832654624694387829/ crashes SeaMonkey and doesn't appear to send a crash report. Turning JavaScript Off the page loads without incident.
...or bug 630197 (see e.g. bug 630197 comment #2)?
Severity: major → critical
Keywords: crash

Comment 3

5 years ago
wfm here, no crash here
User agent: Mozilla/5.0 (Windows NT 5.2; rv:15.0) Gecko/20120909 Firefox/15.0.1 SeaMonkey/2.12.1
Build identifier: 20120909051100
Is this reproducible for you in safe mode (Help - Restart with Add-ons Disabled)?
wfm with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 SeaMonkey/2.16a1

The site seems to load a flash applet. Which flash plugin version do you have installed ?

Comment 5

5 years ago
(In reply to Matthias Versen [:Matti] from comment #4)
> wfm with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0
> Firefox/19.0 SeaMonkey/2.16a1
> 
> The site seems to load a flash applet. Which flash plugin version do you
> have installed ?

willprot doesn't reply.

if  you don't get a crash report, please get a stacktrace
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Keywords: stackwanted
Resolution: --- → INCOMPLETE
(Reporter)

Comment 6

5 years ago
Just FYI it was definitely javascript related but it seems they fixed on the site level, so now it is hard to know what was happening though javascript that would cause the whole browser to shut down. I believe I tried the page in Firefox prior to the fix and it would not crash but can't say for sure now. I will say this I  have seen it happen on another site previous to this but I didn't bug it until it happen with the above site. All I can say is it may be due to an error in javascript code that SeaMonkey can't handle most likely a memory leak, that said while clearly a site issue should not crash SeaMonkey if a site realizes their error they will most likely fix it an as such it's not easy to diagnose. If it comes up again I'll get more info but waiting to spot one error most likely caused by another may be a little time coming.
You need to log in before you can comment on or make changes to this bug.