Closed
Bug 1164241
Opened 9 years ago
Closed 8 years ago
crash in mozilla::gmp::ParseNextRecord(nsILineInputStream*, nsCString const&, nsCString&, bool&)
Categories
(Core :: Audio/Video: GMP, defect, P1)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cpearce, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-ad4734c8-86aa-4180-a7fc-3c7812150512. ============================================================= See also: https://crash-stats.mozilla.com/signature/?signature=mozilla%3A%3Agmp%3A%3AParseNextRecord%28nsILineInputStream*%2C+nsCString+const%26%2C+nsCString%26%2C+bool%26%29&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&page=1 Crashing Firefox, not the plugin-container.
- 10 crashes on the same date, and what looks like the same machine, - Cannot find obvious reason for crash (there are appropriate checks before crash point). -> Should not block EME. Will stop investigating, but keeping it open in case more crashes occur and give more information.
Assignee: gsquelart → nobody
No longer blocks: EME
Status: ASSIGNED → NEW
Summary: [EME] crash in mozilla::gmp::ParseNextRecord(nsILineInputStream*, nsCString const&, nsCString&, bool&) → crash in mozilla::gmp::ParseNextRecord(nsILineInputStream*, nsCString const&, nsCString&, bool&)
|
||
Updated•9 years ago
|
Crash Signature: [@ mozilla::gmp::ParseNextRecord(nsILineInputStream*, nsCString const&, nsCString&, bool&)] → [@ mozilla::gmp::ParseNextRecord(nsILineInputStream*, nsCString const&, nsCString&, bool&)]
[@ mozilla::gmp::ParseNextRecord]
|
||
Updated•9 years ago
|
Component: Audio/Video → Audio/Video: MSG/cubeb/GMP
|
||
Updated•8 years ago
|
Component: Audio/Video: MediaStreamGraph → Audio/Video: GMP
|
|
||
Comment 2•8 years ago
|
||
No indication of any further crashes since the 10 (though it's a pain to search old reports in crashstats, so I may have missed some).
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•