Closed
Bug 1426395
Opened 5 years ago
Closed 5 years ago
Crash in mozilla::dom::cache::ReadStream::Inner::EnsureStream
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jya, Unassigned)
References
Details
(Keywords: regression)
Crash Data
Reporter | ||
Updated•5 years ago
|
Crash Signature: [ @mozilla::dom::cache::ReadStream::Inner::EnsureStream ] → [@mozilla::dom::cache::ReadStream::Inner::EnsureStream]
Comment 1•5 years ago
|
||
This code needs to handle spurious wakeups from the condition variable: https://en.wikipedia.org/wiki/Spurious_wakeup
Assignee: nobody → bkelly
Status: NEW → ASSIGNED
Comment 2•5 years ago
|
||
I guess the problem is actually this, instead: MOZ_CRASH(Blocking read on the js/ipc owning thread!)
Comment 3•5 years ago
|
||
Or maybe its not comment 2 since the stack trace is non-main-thread and also doesn't show anything about worker threads.
Updated•5 years ago
|
Summary: Crasn in mozilla::dom::cache::ReadStream::Inner::EnsureStream → Crash in mozilla::dom::cache::ReadStream::Inner::EnsureStream
Comment 4•5 years ago
|
||
This seems like broken TLS to me. I've seen some other low-frequency crashes recently that also seemed related to TLS not working correctly.
Comment 5•5 years ago
|
||
This also hasn't had any crashes in 57 release channel for some reason. I think I'm going to monitor this for now. Its unclear what we can do here.
Blocks: ServiceWorkers-stability
Comment 6•5 years ago
|
||
Its also possible the ReadableStream is garbage I suppose and the TLS check is failing because mOwningEventTarget is a bad pointer.
Updated•5 years ago
|
Priority: -- → P3
Updated•5 years ago
|
status-firefox58:
--- → affected
Updated•5 years ago
|
Comment 7•5 years ago
|
||
https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals
status-firefox59:
--- → ?
Updated•5 years ago
|
Severity: normal → critical
Comment 8•5 years ago
|
||
I'm not actively working this. Its very low frequency and I don't have any good options to move forward at the moment.
Assignee: bkelly → nobody
Status: ASSIGNED → NEW
Updated•5 years ago
|
Severity: critical → major
Comment 9•5 years ago
|
||
(a reduction in crash frequency or bug priority shouldn't change bug Severity) No crashes in version 61, i.e. after 60.0.2. So => WFM? https://crash-stats.mozilla.com/signature/?signature=mozilla%3A%3Adom%3A%3Acache%3A%3AReadStream%3A%3AInner%3A%3AEnsureStream&date=%3E%3D2018-06-05T03%3A45%3A45.000Z&date=%3C2018-09-05T03%3A45%3A45.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=-date&page=1#reports
Severity: major → critical
Flags: needinfo?(overholt)
Comment 10•5 years ago
|
||
Thanks, Wayne.
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(overholt)
Resolution: --- → WORKSFORME
Assignee | ||
Updated•4 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•