Closed Bug 1306268 Opened 8 years ago Closed 6 years ago

(Don't log handles at shutdown) Crash in shutdownhang | mozilla::CondVar::Wait | mozilla::net::ShutdownEvent::PostAndWait

Categories

(Core :: Networking: Cache, defect, P2)

x86
Windows XP
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox49 --- affected
firefox50 --- affected
firefox51 --- affected
firefox52 --- wontfix

People

(Reporter: mayhemer, Unassigned)

Details

(Keywords: crash, Whiteboard: [necko-next])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-0729b9de-552d-4692-8037-37e0d2160928.
=============================================================

RFindChar2
nsLocalFile::GetLeafName(nsAString_internal&)
nsLocalFile::GetNativeLeafName(nsACString_internal&)
mozilla::net::CacheFileHandle::Log()
mozilla::net::CacheFileIOManager::ShutdownInternal()
mozilla::net::ShutdownEvent::Run()

Not a high rate, but still, found some.
Whiteboard: [necko-next]
Crash volume for signature 'shutdownhang | mozilla::CondVar::Wait | mozilla::net::ShutdownEvent::PostAndWait':
 - nightly (version 52): 1 crash from 2016-09-19.
 - aurora  (version 51): 1 crash from 2016-09-19.
 - beta    (version 50): 124 crashes from 2016-09-20.
 - release (version 49): 1699 crashes from 2016-09-05.
 - esr     (version 45): 0 crashes from 2016-06-01.

Crash volume on the last weeks (Week N is from 10-03 to 10-09):
            W. N-1  W. N-2
 - nightly       1       0
 - aurora        1       0
 - beta         98      26
 - release    1444     255
 - esr           0       0

Affected platform: Windows

Crash rank on the last 7 days:
           Browser     Content   Plugin
 - nightly #527
 - aurora  #2123
 - beta    #154
 - release #24
 - esr
Too late for firefox 52, mass-wontfix.
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P2
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
You need to log in before you can comment on or make changes to this bug.