Closed Bug 1277998 Opened 4 years ago Closed 3 years ago

[Mac OS X] Crashes with IPCError-content | (msgtype=0xE,name=???) Route error: message sent to unknown actor ID

Categories

(Core :: Panning and Zooming, defect, P2, critical)

Unspecified
macOS
defect

Tracking

()

RESOLVED FIXED
Tracking Status
e10s + ---
firefox47 --- unaffected
firefox48 --- wontfix
firefox49 --- wontfix
firefox50 --- fixed
firefox51 --- unaffected

People

(Reporter: dbaron, Unassigned)

Details

(Keywords: crash, topcrash, Whiteboard: [btpp-followup-2016-07-05][gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-2ac8a200-d4cc-4615-8979-1a8f22160602.
=============================================================

There are a small but persistent number of these crashes.  They're on Mac OS X only, so the numbers are small, but we've been averaging about 1 crash per nightly build for the past month.

They're mostly spread across sub-versions of OS X 10.11.*, although there was one crash on 10.10.5.

Bill, do you know who the right person to look into this is?
Flags: needinfo?(wmccloskey)
The earliest report was on build ID 20160429030215 (49.0a1, nightly), but it has been reported on aurora (earliest occurrence in build 20160519004038, 48.0a2).  Does not occur on other channels.
I think Kan-Ru's team might have been looking at some issues like this. I'm not sure though.
Flags: needinfo?(wmccloskey) → needinfo?(kchen)
Whiteboard: btpp-followup-2016-07-05
https://crash-stats.mozilla.com/report/index/938427de-8bdd-4aa9-b496-8eadb2160718 showed up when reviewing the nightly crash stats - so this continues in small volume.

Jim also filed Bug 1285309 which is a similar signature on Windows.
Crash volume for signature 'IPCError-content | (msgtype=0xE,name=???) Route error: message sent to unknown actor ID':
 - nightly (version 50): 47 crashes from 2016-06-06.
 - aurora  (version 49): 213 crashes from 2016-06-07.
 - beta    (version 48): 7 crashes from 2016-06-06.
 - release (version 47): 0 crash from 2016-05-31.
 - esr     (version 45): 0 crash from 2016-04-07.

Crash volume on the last weeks:
             Week N-1   Week N-2   Week N-3   Week N-4   Week N-5   Week N-6   Week N-7
 - nightly          0          4          5         10          7          8         13
 - aurora          40         27         34         26         22         25          4
 - beta             2          1          0          0          1          3          0
 - release          0          0          0          0          0          0          0
 - esr              0          0          0          0          0          0          0

Affected platforms: Windows, Mac OS X, Linux
Blocks: e10s-addons
Flags: needinfo?(kchen) → needinfo?(jmathies)
On beta this is:
proto: PAPZMsgStart
msg: Msg_NotifyAPZStateChange__ID
Component: IPC → Graphics
Flags: needinfo?(jmathies) → needinfo?(bugmail)
No longer blocks: e10s-addons
Thus far I don't see any crashes in Nightly 51 or Aurora 50 with this signature. It may have been fixed already? There are a bunch in Nightly 50, the last one on buildid 20160705030222. Considering 50 was on Nightly until 20160801 or so, that's almost a month of Nightly where this doesn't appear, so it's likely this was fixed in Nightly sometime after July 5th.

I'll leave this open for now; we might want to consider chasing down the fix and uplifting.
Component: Graphics → Panning and Zooming
Flags: needinfo?(bugmail)
Priority: -- → P2
Whiteboard: btpp-followup-2016-07-05 → [btpp-followup-2016-07-05][gfx-noted]
So 20160705030222 is still the last build with one of these crashes. Assuming it was fixed in the next nightly that gives us this range (July 5 - July 6 nightlies):

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c9a70b64f2faa264296f0cc90d68a2ee2bac6ac5&tochange=95ffbc4ff63584631c408e8d9912961fcf68bb09

But since it wasn't that frequent on those builds anyway we might want to expand the range by an extra day to this:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c9a70b64f2faa264296f0cc90d68a2ee2bac6ac5&tochange=4764b9f8e6d4ef9823237f01ca3901759ce8daeb

Nothing really jumped out at me in that range, but if somebody else wants to look through it feel free. If we find the fix we can uplift it to 49. 50 and up are already fixed.
I am calling this resolved fixed since there have been no crashes reported beyond Firefox 49.0.2 in the last month.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.