On 09-10-30 11:34 PM, Phillip Jones wrote:
here is the item in the last crash:
<http://crash-stats.mozilla.com/report/index/bp-4a35ff2f-41ee-4e1e-8a8f-e0cc12091029>
Okay, here's how to use about:crashes to assess the cause of a crash:
1. In the SeaMonkey browser, type about:crashes in the location bar, and
press <Enter>. A page displaying your crash reports will appear.
2. Each crash report is a link, so click the crash report you want to
investigate. This will take to a URL starting with
"http://crash-stats.mozilla.com/..."; It may take some time for your
report to be processed.
3. In your crash report, copy the crash "Signature". You can find it at
the top, just underneath the ID.
4. Go to <https://bugzilla.mozilla.org/query.cgi?format=advanced>, and
paste the crash signature in the summary. Deselect everything under
"Resolution:" and click [Search]. You should get a list of bugs for that
crash signature.
NOTE: In most cases, there is already a link to related bugs in the
crash report. For example, see
<http://crash-stats.mozilla.com/report/index/66904c4a-5eb5-4752-8dea-6d5fc2091030>.
5. Read the comments in the bug. Some of it may not be useful, but
sometimes there's very useful info. For instance,
<https://bugzilla.mozilla.org/show_bug.cgi?id=501429> says the crash for
that bug is caused by Google Talk.
Your crash:
The signature for your latest crash report is
imgLoader::RemoveFromCache(imgCacheEntry*) . Unfortunately, searching
bugzilla does not turn up much for that crash sig. The only bug with
that crash sig is <https://bugzilla.mozilla.org/show_bug.cgi?id=478009>.
It was marked as a dupe of
<https://bugzilla.mozilla.org/show_bug.cgi?id=476349>. Both bugs don't
give much info, and it looks like the original bug may need to be re-opened.
What you can tell is that it is not caused by a plugin or extension. I'm
*guessing* that it's a javascript issue (which makes sense, given that
JS engine in SM2 is completely different). If you continue to get this
crash, one thing you could try is setting the pref
|javascript.options.jit.chrome| to false.
If that doesn't fix it, try setting |javascript.options.jit.content| to
false.
--
Chris Ilias <http://ilias.ca>
List-owner: support-firefox, support-thunderbird, test-multimedia
Keeper of the Knowledge Base: <https://support.mozilla.com/kb/>
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
