Closed Bug 1273658 Opened 9 years ago Closed 9 years ago

Crash in xul.dll@0xabeeb0 | PR_NativeRunThread | pr_root

Categories

(Core :: General, defect)

49 Branch
All
Windows
defect
Not set
critical

Tracking

()

RESOLVED INVALID
Tracking Status
firefox49 + fixed

People

(Reporter: tracy, Unassigned)

Details

(Keywords: crash, regression, topcrash-win)

Crash Data

Combined signatures, this is the #1 crash currently on Nightly wth 334 crashes reported since 2016-05-12 This bug was filed from the Socorro interface and is report bp-01f6c55c-b905-4983-9378-602c12160513. ============================================================= Frame Module Signature Source 0 xul.dll xul.dll@0xabeeb0 1 nss3.dll PR_NativeRunThread nsprpub/pr/src/threads/combined/pruthr.c:397 2 nss3.dll pr_root nsprpub/pr/src/md/windows/w95thred.c:95 Ø 3 ucrtbase.dll ucrtbase.dll@0x6be1c Ø 4 kernel32.dll kernel32.dll@0x159bc Ø 5 ntdll.dll ntdll.dll@0x2a2e0 Ø 6 kernel32.dll kernel32.dll@0x9ba9f Ø 7 kernel32.dll kernel32.dll@0x9ba9f seen on Windows 7, 8, 8.1 and 10 on Nightly 49.0a1
Component: XUL → General
Crash Signature: [@ xul.dll@0xabeeb0 | PR_NativeRunThread | pr_root] [@ xul.dll@0xac77dc | PR_NativeRunThread | pr_root] [@ xul.dll@0xa616f2 | PR_NativeRunThread | pr_root] [@ xul.dll@0xab165e | PR_NativeRunThread | pr_root] → [@ xul.dll@0xabeeb0 | PR_NativeRunThread | pr_root] [@ xul.dll@0xac77dc | PR_NativeRunThread | pr_root] [@ xul.dll@0xa616f2 | PR_NativeRunThread | pr_root] [@ xul.dll@0xab165e | PR_NativeRunThread | pr_root] [@ xul.dll@0xa6a426 | PR_NativeRunThread | …
Found a couple other signatures seemingly related to this issue.
Crash Signature: pr_root] → pr_root] [@ xul.dll@0xa6beca | PR_NativeRunThread | pr_root]
[Tracking Requested - why for this release]: Nominating to track since this is such an explosive crash. As a note, this currently has 474 reports in the last week with combined signatures which makes this the #1 topcrash in Firefox 49 by far, accounting for 13.76% of the overall crash volume. Based on data it looks like this might have started with Nightly 20160512030253 which would assume the following pushlog. https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=674a552743785c28c75866969aad513bd8eaf6ae&tochange=c3f5e6079284a7b7053c41f05d0fe06ff031db03
Keywords: regression
We can track this for now, but comments in https://groups.google.com/a/mozilla.com/forum/#!topic/projectuptime-team/or0j02gUxm0 indicated that there is a symbols issue going on, so until that gets fixed we may not exactly what these crashes are (and the signatures will change).
This is probably just invalid then. The signatures here happened on one build each. No reports since the fix in bug 1272278 landed. Hopefully these shutdown hangs are getting picked up in proper signatures.
(In reply to Tracy Walker [:tracy] from comment #4) > This is probably just invalid then. The signatures here happened on one > build each. No reports since the fix in bug 1272278 landed. Hopefully > these shutdown hangs are getting picked up in proper signatures. I can leave this open until we confirm they are - and I also pinged ted in the other bug about reprocessing the crashes to get the right signatures.
Closing this one out as invalid - as twalker mentions in Comment 4 these signatures stopped happening - and after reviewing crash stats today things look good - so I think we are OK here.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.