Closed
Bug 1259192
Opened 9 years ago
Closed 5 years ago
crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::net::PHttpChannelChild::FatalError | mozilla::net::PHttpChannelChild::OnMessageReceived
Categories
(Core :: Networking, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: elan, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [necko-backlog])
Crash Data
This bug was filed from the Socorro interface and is
report bp-e56984e3-1431-4858-bf44-612e52160312.
=============================================================
Reporter | ||
Comment 1•9 years ago
|
||
:jduell, e10s top crash can you find an assignee?
Flags: needinfo?(jduell.mcbugs)
Comment 2•9 years ago
|
||
I wonder why the message argument to NS_RUNTIMEABORT wasn't included in the crash report...
Putting this on the backlog for now, Jason, feel free to make active once we have an assignee
Whiteboard: [necko-backlog]
Updated•9 years ago
|
Blocks: e10s-crashes
Comment 4•9 years ago
|
||
(In reply to Josh Matthews [:jdm] from comment #2)
> I wonder why the message argument to NS_RUNTIMEABORT wasn't included in the
> crash report...
That's bug 1236108 and its dependencies.
Comment 5•9 years ago
|
||
It looks like this shows up slightly differently on Nightly due to differences in inlining, I assume.
Crash Signature: [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::net::PHttpChannelChild::FatalError | mozilla::net::PHttpChannelChild::OnMessageReceived] → [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::net::PHttpChannelChild::FatalError | mozilla::net::PHttpChannelChild::OnMessageReceived]
[@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::net::PHttpChannelChil…
Comment 6•9 years ago
|
||
Assuming my line numbers match up, that's crashing here:
if ((!(Read((&(cacheKey)), (&(msg__)), (&(iter__)))))) {
FatalError("Error deserializing 'uint32_t'");
Updated•9 years ago
|
Assignee: nobody → kchen
Updated•9 years ago
|
Flags: needinfo?(jduell.mcbugs)
Updated•9 years ago
|
Priority: -- → P1
Comment 7•9 years ago
|
||
Signature will be changed to OOM by bug 1258312.
Close for now. If the signature shows up again we could reopen.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Comment 8•9 years ago
|
||
Nightly 20160429030215 had 12 occurrences of
https://crash-stats.mozilla.com/report/index/9edbd88b-a899-467f-a91f-9e4522160430, but there were all from a single user.
Kan-Ru, I'm needinfo'ing you in case you want to take a look.
Flags: needinfo?(kchen)
Comment 9•9 years ago
|
||
I took a look and found the error is "[Child 1036] ###!!! ABORT: IPDL error [PHttpChannelChild]: \"Error deserializing 'NetAddr'\". abort()ing as a result." on Msg_OnStartRequest
In NeckoMessageUtils.h there is one comment:
/* If we get here without hitting any of the cases above, there's not much
* we can do but let the deserializer fail when it gets this message */
https://dxr.mozilla.org/mozilla-central/rev/0a25833062a880f369e6f9f622413a94cc671bf4/netwerk/ipc/NeckoMessageUtils.h#101-102
I'm not sure if we are hitting this path but it seems better to crash in the Write side instead of the Read side.
Updated•9 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 10•9 years ago
|
||
I see 8 more crashes in the 5/02 build, so clearly this is an ongoing issue.
(In reply to Kan-Ru Chen [:kanru] (UTC+8) from comment #9)
> I'm not sure if we are hitting this path but it seems better to crash in the
> Write side instead of the Read side.
Definitely! Crashing in the Write() could give the information the Necko team needs to fix whatever is going wrong.
Comment 11•9 years ago
|
||
On Nightly, there were many crashes on 5-2, and many on 5-3 build, but none since then. However, the 5-2 crashes are all with a single install time, as are those on the 5-3 build, so it seems like this is all due to one or maybe two users.
Comment 12•9 years ago
|
||
Comment 13•9 years ago
|
||
(In reply to Jim Mathies [:jimm] from comment #12)
> On beta 47 this is currently #24 -
Looking at the 63 crashes in there, I'd say the majority of the crashes have a single install time, suggesting a single unlucky persistent user.
Updated•9 years ago
|
Flags: needinfo?(kchen)
Updated•8 years ago
|
Assignee: kchen → nobody
Priority: P1 → P4
Comment 14•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P4 → P1
Comment 15•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Comment 16•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•