Closed
Bug 1268536
Opened 8 years ago
Closed 8 years ago
null-dereference crashes in nsAboutCacheEntry::OnStartRequest
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
DUPLICATE
of bug 1266196
People
(Reporter: dbaron, Assigned: dragana)
Details
(Keywords: crash, Whiteboard: [necko-active])
Crash Data
This bug was filed from the Socorro interface and is report bp-2835e9ce-d82a-4e98-89be-e74442160428. ============================================================= There are a small number of crashes reported (single digit number per release cycle, mixed between channels from nightly to esr) in nsAboutCacheEntry::OnStartRequest. They're all null-dereference crashes, with null mOutputStream (although I only double-checked the minidump of one to verify that it was mOutputStream that's null -- but I also don't see other things that could be on that line). A query is: https://crash-stats.mozilla.com/signature/?product=Firefox&date=%3E%3D2015-09-01&signature=nsAboutCacheEntry%3A%3AOnStartRequest&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&page=2 I figured even though they're rare, it's worth filing, since it may be obvious how to handle null here or how to avoid getting here with a null pointer.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → dd.mozilla
Whiteboard: [necko-active]
Assignee | ||
Comment 1•8 years ago
|
||
From Honza's comment in bug 1266196, he is going to fix this issue there as well. So I will make this dup of that bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•