Closed
Bug 1330901
Opened 7 years ago
Closed 7 years ago
Exception in GCTelemetry.jsm
Categories
(Core :: JavaScript: GC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1328198
Tracking | Status | |
---|---|---|
firefox-esr45 | --- | unaffected |
firefox50 | --- | unaffected |
firefox51 | --- | unaffected |
firefox52 | --- | affected |
firefox53 | --- | affected |
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
Details
Attachments
(1 file)
7.84 KB,
application/json
|
Details |
The following error is repeatedly emitted on the browser console on a session without addons:
> SyntaxError: JSON.parse: expected double-quoted property name at line 1 column 46 of the JSON data[Learn More] GCTelemetry.jsm:194:16
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
I'm also seeing this issue, and I've attached an example of the problematic JSON data above (please refer to GCTelemetry_error.json). The error comes from http://searchfox.org/mozilla-central/rev/0aed9484bd3e97206fd1949ee4a4992ef300a81f/toolkit/components/telemetry/GCTelemetry.jsm#194, which thus points to bug 1308040. In general it's probably not meaningful to speculate about what the issue could be, however one perhaps useful data point: I'm using Windows 7 (64-bit) with a Swedish locale. Note that in Sweden we use decimal comma, instead of decimal point as in e.g. English speaking countries, and I cannot help wondering if some part of the JSON building algorithm used (indirectly) by GCTelemetry.jsm could perhaps depend on the locale!?
Blocks: 1308040
status-firefox50:
--- → unaffected
status-firefox51:
--- → unaffected
status-firefox52:
--- → affected
status-firefox-esr45:
--- → unaffected
tracking-firefox52:
--- → ?
tracking-firefox53:
--- → ?
Component: General → JavaScript: GC
Flags: needinfo?(wmccloskey)
Product: Firefox → Core
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
tracking-firefox52:
? → ---
tracking-firefox53:
? → ---
Flags: needinfo?(wmccloskey)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•