Closed Bug 686441 Opened 8 years ago Closed 7 years ago
Crash in JSLinear
String::mark(JSTracer*) or JSString::mark(JSTracer*) mainly with Better Facebook
Crash Signature: [@ JSLinearString::mark(JSTracer*) ] [@ JSString::mark(JSTracer*) ]
Confirming this based on data in crash stats. Also see related Bug 687001 which appears to be the Mac version of this signature. Reporter: Are you using the Better Facebook extension?
Status: UNCONFIRMED → NEW
Ever confirmed: true
It's #21 top crasher in 7.0.1 and #20 in 8.0b1. There's an extension correlation in 7.0.1: JSLinearString::mark(JSTracer*)|EXCEPTION_ACCESS_VIOLATION_READ (236 crashes) 79% (187/236) vs. 1% (406/57390) firstname.lastname@example.org 0% (0/236) vs. 0% (1/57390) 5.852 0% (0/236) vs. 0% (2/57390) 5.911 1% (2/236) vs. 0% (3/57390) 5.921 42% (98/236) vs. 0% (228/57390) 5.931 37% (87/236) vs. 0% (172/57390) 5.941
Summary: Crash in JSLinearString::mark(JSTracer*) or JSString::mark(JSTracer*) → Crash in JSLinearString::mark(JSTracer*) or JSString::mark(JSTracer*) mainly with Better Facebook
no crashes for JSLinearString::mark(JSTracer*) after version 10.0.2. any correlations still show for betterfacebook or http://socialfixer.com/blog/2011/11/08/better-facebook-is-now-social-fixer/ ? perhaps signature superseded by one of these? https://crash-stats.mozilla.com/query/query?product=Firefox&version=Firefox%3A22.0a1&version=Firefox%3A21.0a2&version=Firefox%3A20.0b5&version=Firefox%3A19.0.2&version=Firefox%3A20.0b4&version=Firefox%3A20.0b3&version=Firefox%3A20.0b2&version=Firefox%3A20.0b1&range_value=1&range_unit=weeks&date=03%2F17%2F2013+00%3A40%3A17&query_search=signature&query_type=contains&query=JSTracer&reason=&build_id=&process_type=any&hang_type=any&do_query=1
I don't see high correlations to BetterFacebook in 19.0.2 for any crash signatures: https://crash-analysis.mozilla.com/crash_analysis/20130316/20130316_Firefox_19.0.2-interesting-addons.txt.gz Based on comment 5 and this comment, I close the bugs as workforme.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.