Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20100101 Firefox/11.0 Crashed once on 11 Beta2 on shutdown. Couldn't reproduce afterwards with the same session or with a clean profile. https://crash-stats.mozilla.com/report/index/bp-0b2294ed-2918-480f-9082-785a52120210 The action that trigerred this: restarting browser after yahoo toolbar installation. Had a pretty intense session: grooveshark.com, facebook, youtube and a flash game all opened. Similar issues: bug 182803 (verified 9 years ago) and bug 700499 (mobile) Thought of logging this for investigation as there are some other reports available under crash-stats.
Crash Signature: [@ nssCertificate_Destroy ]
Marcia, is there anything in crashstats we can use to investigate this further?
Here are the first frames of the stack: Frame Module Signature [Expand] Source 0 nss3.dll nssCertificate_Destroy security/nss/lib/pki/certificate.c:134 1 nss3.dll CERT_DestroyCertificate security/nss/lib/certdb/stanpcertdb.c:823 2 nss3.dll DPCache_Destroy security/nss/lib/certdb/crl.c:1162 3 nss3.dll IssuerCache_Destroy security/nss/lib/certdb/crl.c:1209 4 nss3.dll FreeIssuer security/nss/lib/certdb/crl.c:1275 5 plds4.dll PL_HashTableEnumerateEntries nsprpub/lib/ds/plhash.c:406 6 nss3.dll ShutdownCRLCache security/nss/lib/certdb/crl.c:1340 7 nss3.dll nss_Shutdown security/nss/lib/nss/nssinit.c:1098 8 nss3.dll NSS_Shutdown security/nss/lib/nss/nssinit.c:1156 9 xul.dll nsNSSComponent::ShutdownNSS security/manager/ssl/src/nsNSSComponent.cpp:1924 10 xul.dll nsNSSComponent::DoProfileBeforeChange security/manager/ssl/src/nsNSSComponent.cpp:2608 11 xul.dll nsNSSComponent::Observe security/manager/ssl/src/nsNSSComponent.cpp:2237 12 xul.dll nsObserverList::NotifyObservers xpcom/ds/nsObserverList.cpp:130 13 mozjs.dll js_GC js/src/jsgc.cpp:3015 14 xul.dll nsXREDirProvider::DoShutdown toolkit/xre/nsXREDirProvider.cpp:814
Severity: normal → critical
Component: General → Security
Product: Firefox → Core
QA Contact: general → toolkit
How reproducible/prevalent is this crash?
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #3) > How reproducible/prevalent is this crash? It's #82 top browser crasher in 11.0b3. It spiked from 11.0a1/20111128 but discontinuously (up to 4 build.days between 2 crashes). The regression range (large version) for the spike is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=84117219ded0&tochange=854aabf544d4 Here are some comments in 11.0: "just switched to aol and was attempting to sign in,i got my login wrong once and was entering it again when it crashed." "Firefox asked to restart the browser in order to install the 11.0 Beta 3 update. Crash occurred after I confirmed." It's correlated to media like in bug 675260: nssCertificate_Destroy|EXCEPTION_ACCESS_VIOLATION_READ (30 crashes) 53% (16/30) vs. 23% (6857/29707) gkmedias.dll
OS: Windows XP → All
Hardware: x86 → All
I don't think #82 top-crash quite qualifies this for tracking yet but we should watch to see if it increases with 11b4. Virgil can you try to identify a reproducible STR/testcase?
tracking-firefox11: --- → ?
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #5) > I don't think #82 top-crash quite qualifies this for tracking yet but we > should watch to see if it increases with 11b4. Virgil can you try to > identify a reproducible STR/testcase? Please re-nominate for tracking if/when this breaks into the top crash range on beta.
tracking-firefox11: ? → -
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #5) > Virgil can you try to identify a reproducible STR/testcase? Tried with 11 beta 6 on Windows XP. As most of the comments in Socorro mentioned games, I tried reproducing with games and media sites: facebook, miniclip.com, grooveshark.com, apple.trailers, www.racing-games.com etc. Also tried loading sites from the profile used when the crash occurred. Unsuccessful so far.
Component: Security → Security: PSM
QA Contact: toolkit → psm
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 700499
You need to log in before you can comment on or make changes to this bug.