Closed
Bug 1426712
Opened 6 years ago
Closed 6 years ago
shutdownhang signature processor is broken
Categories
(Socorro :: Backend, task)
Socorro
Backend
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mccr8, Unassigned)
References
Details
These shutdown hang reports are being reported as [@ IPCError-browser | ShutDownKill] now. I still see at least one instance of a shutdownhang ( bp-2c4ceef6-6ee3-4995-bb35-54aea0171220 ) but mostly they are not. Trevor Skywalker seems to have noticed this first on 12-8 in bug 1424451.
Reporter | ||
Comment 1•6 years ago
|
||
It is possible that I'm completely confused about this and shutdownhang was not the top crash.
Reporter | ||
Comment 2•6 years ago
|
||
Hmm never mind. I went back and looked at older reports, and I guess this was always the signature. Sorry for the confusion.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
Comment 3•6 years ago
|
||
I don't think the processor for shutdownhang signature is broken. There are still many signatures containing "shutdownhang". https://crash-stats.mozilla.com/search/?signature=shutdownhang&product=Firefox&date=%3E%3D2017-12-15T23%3A12%3A47.000Z&date=%3C2017-12-22T23%3A12%3A47.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature Shows 50 signatures containing the term "shutdownhang" accounting for 186,115 Crash Reports over the past 7 days. --- Shutdownhang crashes are still top crashers though. Do they have a [meta] bug to help with organization? (Should they have a [meta] bug?) Looking at Top Crashers for Firefox 57.0.2 Top 300 Crashing Signatures. 7 days ago https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0.2&_facets_size=300 Find (Ctrl+F) "shutdownhang" shows 112 matches out of 300 results. So about a third of all top crash signatures are related to "shutdownhang". Out of the top 30 there are 14 with "shutdownhang" (or about half). 3 2.48% -0.07% shutdownhang | mozilla::layers::CompositorThreadHolder::Shutdown application 4029 4029 0 0 3794 0 2016-11-10 5 1.62% -0.12% shutdownhang | mozilla::SpinEventLoopUntil<T> | mozilla::net::nsHttpConnectionMgr::Shutdown application 2626 2626 0 0 2441 0 2017-10-25 8 1.4% -0.02% shutdownhang | nsThread::Shutdown | nsThreadManager::Shutdown yellow flag application 2264 2264 0 0 2277 0 2017-09-27 9 1.31% 0.08% shutdownhang | mozilla::dom::quota::QuotaManager::ShutdownObserver::Observe application 2128 2128 0 0 1910 0 2016-04-14 11 1.04% -0.02% shutdownhang | NtQueryAttributesFile application 1682 1682 0 0 1722 0 2015-01-21 13 0.9% -0.14% shutdownhang | `anonymous namespace''::ParentImpl::ShutdownBackgroundThread application 1463 1463 0 0 1432 0 2017-09-28 15 0.84% -0.08% shutdownhang | mozilla::dom::workers::RuntimeService::Cleanup application 1363 1363 0 0 1296 0 2015-10-31 16 5 0.81% -0.11% shutdownhang | nsAppShell::ProcessNextNativeEvent application 1318 1318 0 0 1405 0 2015-10-20 19 0.73% 0.03% shutdownhang | PR_MD_WAIT_CV | PR_Wait | mozilla::ReentrantMonitor::Wait | mozilla::layers::SynchronousTask::Wait application 1191 1191 0 0 1200 0 2016-11-23 22 5 0.61% -0.09% shutdownhang | mozilla::SpinEventLoopUntil<T> | nsThread::Shutdown | nsThreadManager::Shutdown yellow flag application 990 990 0 0 916 0 2017-10-25 24 8 0.54% -0.06% shutdownhang | NtUserMsgWaitForMultipleObjectsEx | CCliModalLoop::BlockFn application 882 882 0 0 842 0 2017-05-15 25 0.53% 0.14% shutdownhang | CCliModalLoop::BlockFn application 863 863 0 0 817 0 2016-08-17 28 6 0.48% -0.03% shutdownhang | mozilla::SpinEventLoopUntil<T> | `anonymous namespace''::ParentImpl::ShutdownBackgroundThread application 783 783 0 0 777 0 2017-10-25 29 8 0.48% -0.06% shutdownhang | nsThreadManager::SpinEventLoopUntil application 780 780 0 0 798 0 2017-09-27 31 0.47% 0.05% shutdownhang | MsgWaitForMultipleObjectsEx | CCliModalLoop::BlockFn application 757 757 0 0 737 0 2016-08-17 32 8 0.45% -0.04% shutdownhang | mozilla::SyncRunnable::DispatchToThread application 725 725 0 0 711 0 2017-07-29
You need to log in
before you can comment on or make changes to this bug.
Description
•