Closed
Bug 1202817
Opened 9 years ago
Closed 8 years ago
crash in mozilla::net::Predictor::OnMetaDataElement(char const*, char const*)
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: WeirdAl, Unassigned)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
5.84 KB,
text/plain
|
Details |
This bug was filed from the Socorro interface and is report bp-85785551-d76b-43e2-b245-77b312150908. =============================================================
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Crashes at http://hg.mozilla.org/releases/mozilla-release/annotate/5500ee2a6206/xpcom/string/nsTSubstring.h#l931 However thanks unification we don't know the caller. Michal, could this be some problem with the metadata buffer?
Flags: needinfo?(michal.novotny)
Updated•9 years ago
|
Crash Signature: [@ mozilla::net::Predictor::OnMetaDataElement(char const*, char const*)] → [@ mozilla::net::Predictor::OnMetaDataElement(char const*, char const*)]
[@ mozilla::net::Predictor::OnMetaDataElement]
Comment 3•8 years ago
|
||
the only instance of this in crash stats in the last week is also from ff40
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Comment 4•8 years ago
|
||
(In reply to Honza Bambas (:mayhemer) from comment #2) > Michal, could this be some problem with the metadata buffer? Metadata buffer handling is taken mostly from the old cache where it worked for years. If it ever happens again we can turn MOZ_ASSERTs that check buffer validity into release asserts.
Flags: needinfo?(michal.novotny)
You need to log in
before you can comment on or make changes to this bug.
Description
•