1319001 - Crash in mozilla::ChannelMediaResource::RecreateChannel

Status: RESOLVED DUPLICATE of bug 1333576

(Core :: Audio/Video: Playback, defect, P1)

Description

[Nicholas Nethercote [inactive]]

This bug was filed from the Socorro interface and is 
report bp-a40c0248-1c48-4308-b8e9-2e27b2161118.
=============================================================

This crash signature has been around at low volume for some time, but there was a moderate increase in Nightly 20161113030203 (which was 52) and then a bigger increase in Nightly 20161114043454 (which is 53).

The crash address is often 0xffffffff, but not always. Sometimes it's something like 0x20. I'm not sure I trust those addresses though, 0xffffffff isn't always reliable. Either way, it looks like |owner| is bogus.

cpearce, any ideas?

Comment 1

[JW Wang [:jwwang] [:jw_wang]]

Hi James,
Can you check this issue? You can load the crash dump using VS to get more details about the stack trace.

Comment 2

[James Cheng[:JamesCheng]]

Unfortunately,
I opened some dump files from [1] by VS, they always show that some of the values cannot be evaluated.
Thus, VS is not helpful for this case to see whom uses the invalid address.

It seems a regression since the crash occurred in these few days on nightly[2].

I know nothing about ChannelMediaResource, could need someone to indicate the direction that can make this bug move forward.

Maybe Chris knew the suspicious point during the recent changes.

[1]
https://crash-stats.mozilla.com/signature/?address=0xffffffffffffffff&signature=mozilla%3A%3AChannelMediaResource%3A%3ARecreateChannel&date=%3E%3D2016-11-15T08%3A31%3A00.000Z&date=%3C2016-11-22T08%3A31%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#reports

[2]
https://crash-stats.mozilla.com/signature/?release_channel=nightly&signature=mozilla%3A%3AChannelMediaResource%3A%3ARecreateChannel&date=%3E%3D2016-08-22T09%3A43%3A52.000Z&date=%3C2016-11-22T09%3A43%3A52.000Z#graphs

Comment 3

[JW Wang [:jwwang] [:jw_wang]]

Bug 1333576 should've fixed this.