Closed
Bug 1409216
Opened 7 years ago
Closed 7 years ago
Crash in google_breakpad::ReceivePort::WaitForMessage | google_breakpad::CrashGenerationClient::RequestDumpForException
Categories
(Core :: Audio/Video: cubeb, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1411866
People
(Reporter: marcia, Assigned: achronop)
References
Details
(Keywords: crash, regression)
Crash Data
This bug was filed from the Socorro interface and is report bp-e9f7582e-e19a-4869-80c2-372890171016. ============================================================= Seen while looking at crash stats: http://bit.ly/2yt0HdD. Crashes started using 20171014100219. Possible regression range based on Build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=196dadb2fe500e75c6fbddcac78106648676cf10&tochange=d71e8e0053d8043bc9deb98b35ca5220a0c9adea Comments: Trying to create a new gcal event.
Updated•7 years ago
|
Priority: -- → P2
Comment 1•7 years ago
|
||
Ales, easy one I think, we're destroying the stream before having incremented, during init.
Flags: needinfo?(acrichton)
Comment 2•7 years ago
|
||
Hm sorry I'm not sure I understand what's going on here :(
Flags: needinfo?(acrichton)
Assignee | ||
Comment 4•7 years ago
|
||
Pushed for review in cubeb repo: https://github.com/kinetiknz/cubeb/pull/367
Assignee: nobody → achronop
Flags: needinfo?(achronop)
Assignee | ||
Updated•7 years ago
|
Rank: 15
Comment 5•7 years ago
|
||
in terms of the regression range - i think bug 1405151 is surfacing the real signature now, before that those crashes would have shown up with an empty signature.
status-firefox57:
--- → affected
Comment 6•7 years ago
|
||
Hi :spohl, Can you help take a look at this issue?
Flags: needinfo?(spohl.mozilla.bugs)
Comment 7•7 years ago
|
||
Comment 5 is explaining why this signature started showing up and this bug is assigned to Alex who has this fixed in cubeb (comment 4). Is there something in particular you wanted me to look into?
Flags: needinfo?(spohl.mozilla.bugs) → needinfo?(gchang)
Comment 8•7 years ago
|
||
this is a frequent content crash on 57.0b on osx - can we uplift the fix?
Flags: needinfo?(achronop)
Comment 9•7 years ago
|
||
Hi :spohl, Thanks for the update. I just noticed comment #4 has a patch.
Flags: needinfo?(gchang)
Assignee | ||
Comment 10•7 years ago
|
||
The fix is landed in cubeb repo. I will do the import in gecko soon.
Flags: needinfo?(achronop)
Reporter | ||
Comment 11•7 years ago
|
||
(In reply to Alex Chronopoulos [:achronop] from comment #10) > The fix is landed in cubeb repo. I will do the import in gecko soon. Alex: Will this also fix crashes such as https://crash-stats.mozilla.com/report/index/fe7d65fd-fc1c-4ee3-a22b-2869f0171024#allthreads? There seem to be a bunch of Mac crashes that I see daily in 58 with signatures like [@ @0x7fff348183b0]. I noticed today that this one has cubeb stuff lower in the threads.
Assignee | ||
Comment 12•7 years ago
|
||
(In reply to Marcia Knous [:marcia - use ni] from comment #11) > Alex: Will this also fix crashes such as > https://crash-stats.mozilla.com/report/index/fe7d65fd-fc1c-4ee3-a22b- > 2869f0171024#allthreads? No it does not look the same. I do not expect to be fixed by that. Usually this kind of signature exist when one component creates a deadlock inside apple's framework. But that's only a guess with such a poor signature.
Assignee | ||
Comment 14•7 years ago
|
||
Sure let me import it first and I will apply for uplift. I am waiting one review in order to import.
Flags: needinfo?(achronop)
Comment 15•7 years ago
|
||
Hi Alex, Does bug 1411866 already fix this one? Should I set this bug as resolved duplicate?
Flags: needinfo?(achronop)
Assignee | ||
Comment 16•7 years ago
|
||
Yeah, this is now fixed. Thanks for pointing out.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(achronop)
Resolution: --- → DUPLICATE
Comment 17•7 years ago
|
||
(In reply to Alex Chronopoulos [:achronop] from comment #16) > Yeah, this is now fixed. Thanks for pointing out. Cheers! :)
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•