Empty Base Profiler profile makes Gecko Profiler profile JSON ill-formed
Categories
(Core :: Gecko Profiler, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox71 | --- | wontfix |
firefox72 | --- | fixed |
People
(Reporter: mozbugz, Assigned: mozbugz)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
When Gecko Profiler grabs a Base Profiler profile, it assumes that it is empty if the string is totally empty:
https://searchfox.org/mozilla-central/rev/581466eef9269afb03d8a0dba2f50215f3a9026c/tools/profiler/core/platform.cpp#3985
However an empty profile results in a JSON with 1 character -- a newline.
Assignee | ||
Comment 1•6 years ago
|
||
... And that caused Gecko Profiler to just blindly "splice" this non-empty looking string into its profile, so the JSON looked like: [ <valid JSON here>, ]
-- Notice the missing object after the comma.
Assignee | ||
Comment 2•6 years ago
|
||
JSON profiles from the Base Profiler were assumed to be empty if they contained
zero characters, but in fact they contain one character (a single newline).
Comment 4•6 years ago
|
||
Backed out for causing MinGW bustages on GeckoProfiler.
Backout link: https://hg.mozilla.org/integration/autoland/rev/bf317b52fd44acd12845db1b4dc5d54bb3d08b4a
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=278302910&repo=autoland&lineNumber=80555
Assignee | ||
Updated•6 years ago
|
Comment 6•6 years ago
|
||
bugherder |
Updated•6 years ago
|
Comment 7•6 years ago
|
||
Hi Gerald, is qa needed here? If so, could you provide us with some steps? Thanks!
Updated•4 years ago
|
Description
•