Closed
Bug 1603824
Opened 4 years ago
Closed 4 years ago
Crash in [@ PR_GetThreadID | mozilla::BackgroundPriorityRegion::Clear]
Categories
(Toolkit :: Telemetry, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1603153
Tracking | Status | |
---|---|---|
firefox72 | --- | unaffected |
firefox73 | --- | fixed |
People
(Reporter: marcia, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-4d3b7f91-ff46-4ff7-9d44-d78150191213.
Seen while looking at night crash stats - Windows crashes which started in 20191210095443: https://bit.ly/35lUjTx. 30 crashes/15 installs so far.
Possible regression range based on build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8a285497c16992995f515e43166432b0c765ea72&tochange=1fb1ca98f23b29d1a8a287ad2db326c84df04c57
Several telemetry related changes in that changeset but not sure which one might be involved. Maybe aklotz can assist.
Top 10 frames of crashing thread:
0 nss3.dll PR_GetThreadID nsprpub/pr/src/threads/prcthr.c:138
1 xul.dll static void mozilla::BackgroundPriorityRegion::Clear toolkit/xre/UntrustedModulesProcessor.cpp:60
2 xul.dll void mozilla::UntrustedModulesProcessor::Disable toolkit/xre/UntrustedModulesProcessor.cpp:140
3 xul.dll nsresult mozilla::UntrustedModulesProcessor::Observe toolkit/xre/UntrustedModulesProcessor.cpp:156
4 xul.dll nsObserverList::NotifyObservers xpcom/ds/nsObserverList.cpp:66
5 xul.dll nsObserverService::NotifyObservers xpcom/ds/nsObserverService.cpp:292
6 xul.dll mozilla::dom::ContentChild::RecvShutdown dom/ipc/ContentChild.cpp:3061
7 xul.dll mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:11059
8 xul.dll void mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2131
9 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1256
Flags: needinfo?(aklotz)
Comment 1•4 years ago
|
||
This is probably a dupe of bug 1603153.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(aklotz)
Resolution: --- → DUPLICATE
Updated•4 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•