Closed Bug 1210547 Opened 9 years ago Closed 9 years ago

crash in mozilla::ipc::FatalError(char const*, char const*, unsigned long, bool) | mozilla::jsipc::PJavaScriptParent::FatalError(char const* const) | mozilla::jsipc::PJavaScriptParent::Read(mozilla::jsipc::JSVariant*, IPC::Message const*, void**)

Categories

(Core :: DOM: Content Processes, defect)

Product:
Core
Component:
DOM: Content Processes
Platform:
x86
Windows
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
e10s ? ---
firefox44 --- affected

People

(Reporter: guijoselito, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-a94d6e9f-8acb-4ece-90f1-36cdf2151001.
=============================================================

I've been using Nightly with e10s off due to some crashes I was hitting.
Yesterday I decided to try it again, but hit a lot of crashes today (I don't know if it's a regression from yesterday or just coincidence).

These crashes were hit sometimes on startup, sometimes after switching tabs right after startup... but all very early.

More of the same:
https://crash-stats.mozilla.com/report/index/bp-553908a5-eff4-4bb8-b550-f1c5d2151001
https://crash-stats.mozilla.com/report/index/bp-035ed643-fedb-4905-8cd7-842b42151001
https://crash-stats.mozilla.com/report/index/bp-b458611f-6e32-4861-9d91-6fe6f2151001
Gullherme, I suspect that an addon caused some of these crashes. Could you try disabling some/all of your addons and see if there is a particular one causing these crashes?
tracking-e10s: --- → ?
Component: IPC → DOM: Content Processes
Flags: needinfo?(guijoselito)
Sorry, I should have tested before... it's just nobody said anything on Mozillazine, so I thought it wasn't possible.

It is indeed due to an addon: Adblock Plus
Flags: needinfo?(guijoselito)
I get it when clicking on links onside any webpage at random.
5 crashes this hour and counting. This crash is going to get old quick.

Very real possibility its caused by Adblock Plus but it is definitely a recent regression in either it or Nightly (was running a Nightly from about 22nd Sept until updating this morning).

I might try non-e10s for a while.
OS: Windows 7 → Windows
This looks like it might be a duplicate of bug 1210821 — the FatalError call is different (an out-of-range union discriminant instead of an unexpected end-of-message) but it could have the same cause.
Hey Guilherme - a fix for bug 1210821 landed in the code today, and if all goes well, tomorrow's Nightly will have the fix in it. Would you mind testing tomorrow's Nightly when you get a chance to see if you still hit the crash? If not, I think jld was right in bug comment 4 about this having the same root cause as the other bug.
Flags: needinfo?(guijoselito)
As pointed out on https://bugzilla.mozilla.org/show_bug.cgi?id=1210821#c12 the crashes didn't go away. I crashed in the same way with today's Nightly: https://crash-stats.mozilla.com/report/index/8c3262ba-0210-4790-b71e-83ab62151007
Flags: needinfo?(guijoselito)
Flags: needinfo?(wmccloskey)
This crash seems to have disappeared with the backout I did.
Flags: needinfo?(wmccloskey)
Crash Signature: [@ mozilla::ipc::FatalError(char const*, char const*, unsigned long, bool) | mozilla::jsipc::PJavaScriptParent::FatalError(char const* const) | mozilla::jsipc::PJavaScriptParent::Read(mozilla::jsipc::JSVariant*, IPC::Message const*, void**)] → [@ mozilla::ipc::FatalError(char const*, char const*, unsigned long, bool) | mozilla::jsipc::PJavaScriptParent::FatalError(char const* const) | mozilla::jsipc::PJavaScriptParent::Read(mozilla::jsipc::JSVariant*, IPC::Message const*, void**)] [@ mozilla::…
Alright Guilherme, according to comment 7, this crash has dropped off recently. Are you still hitting it?
Flags: needinfo?(guijoselito)
Not anymore, since the first build with the backouts.
Flags: needinfo?(guijoselito)
Closing WFM as per comment 9.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.