Closed
Bug 1353349
Opened 7 years ago
Closed 7 years ago
Blank view when trying to retrieve profile; console shows "TypeError: e.meta is undefined"
Categories
(Core :: Gecko Profiler, defect)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: lth, Assigned: mstange)
Details
Attachments
(1 file)
When typing Ctrl-Shift-2 to retrieve the profile a new tab is shown with the text "Retrieving profile from the gecko profiler addon..." at the top and nothing else. The page is never filled in. The console shows this text: TypeError: e.meta is undefined ... 930ab849cc46f3f9ae82.bundle.js:28:6949 Successfully compiled asm.js code (loaded from cache in 4ms) zee-worker.js This is in Dev Ed 54 and Nightly 55, both up-to-date as of today and Gecko Profiler installed today. Mac OS X 10.12.3, "late 2013" MBP, lots of RAM.
Assignee | ||
Comment 1•7 years ago
|
||
Does the problem go away if you reload the perf-html.io tab?
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to Markus Stange [:mstange] from comment #1) > Does the problem go away if you reload the perf-html.io tab? It does not.
Reporter | ||
Comment 3•7 years ago
|
||
And I did have an adblocker enabled early on, but I've since disabled that. My Nightly profile only has the Gecko Profiler, uBlock Origin, and Duplicate In Tab Context Menu extensions.
Assignee | ||
Comment 4•7 years ago
|
||
I don't know what might be causing this. May I ask you to do some debugging using a development version of perf.html? You can follow the steps on https://github.com/devtools-html/perf.html#development to launch your own instance locally and point the add-on at it.
Reporter | ||
Comment 5•7 years ago
|
||
Will try to find some time this week for that. Thanks.
Comment 6•7 years ago
|
||
I ran into this same issue a few days ago. In the development version it was `profile.meta`. I believe the profile we got from the Gecko Profiler Addon was a blank object `{}`.
Assignee | ||
Comment 7•7 years ago
|
||
I've now hit this a few times myself. It looks like the platform is generating invalid JSON, failing to parse it, and then returning an empty object from getProfileDataAsync().
Comment hidden (mozreview-request) |
Comment 9•7 years ago
|
||
mozreview-review |
Comment on attachment 8866023 [details] Bug 1353349 - Don't attempt to put empty profiles into the processes array. https://reviewboard.mozilla.org/r/137616/#review140738 Willing to say this is a good thing, though it doesn't fix the issue I'm seeing.
Attachment #8866023 -
Flags: review?(nfroyd) → review+
Comment 10•7 years ago
|
||
Pushed by mstange@themasta.com: https://hg.mozilla.org/integration/autoland/rev/dba495fc3c06 Don't attempt to put empty profiles into the processes array. r=froydnj
Comment 11•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/dba495fc3c06
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Comment 12•7 years ago
|
||
I meet this issue in Fx55b1 x64 on Win10 now, I once encountered it in Nightly 55 and it once gone away.
Updated•6 years ago
|
Assignee: nobody → mstange
You need to log in
before you can comment on or make changes to this bug.
Description
•