Sometimes the profiler doesn't process the captured stacks unless you restart Nightly
Categories
(Core :: Gecko Profiler, defect, P2)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
Details
Attachments
(1 file)
|
38.23 KB,
text/plain
|
Details |
I dont know the correct terminology
- Use nightly
- Press ctrl+shift+1 to begin a capture
- Do the stuff you want to profile
- Press ctrl+shift+2
- A new tab will open with the URL https://profiler.firefox.com/from-addon/
And thats it. The page never proceeds further than this. In a bug-free mode, the URL "callstack v5" would be appended to the URL, and then the usual processing would take place.
If I try to close nightly at this stage, nightly process keeps on running.
I am unable to capture profiles until i restart nightly.
This is an intermittent bug.
By "that's it", do you mean that the tab stays completely empty?
I think I see something similar sometimes, but restarting the profiler (without restarting Nightly itself) usually works for me.
It will be difficult to debug. We should add more diagnostic information in the js console to try and catch what goes wrong...
Greg, you know more about the interaction between the Gecko Profiler and the receiving profiler.firefox.com tab, would you have any ideas or suggestions?
|
Reporter | |
Comment 2•4 years ago
|
||
tab doesnt stay "blank". It shows the page animation of the horizontal lines fading in-and-out. The page doesnt progress beyond that, though.
|
||
Comment 3•4 years ago
|
||
(In reply to Mayank Bansal from comment #0)
If I try to close nightly at this stage, nightly process keeps on running.
This seems similar to what I was describing in bug 1675068 comment 1.
|
||
Comment 4•4 years ago
|
||
The frame script injection is very naive, and we do not really surface up any information about what's going on in this process. I'm hesitant to mess with the frame script to add new features, but we should explore Bug 1625309, and then see if we can use more of a dialog between the Gecko Profiler an the front-end so that we know the status of things. Right now errors are really hard to debug.
|
|
||
Comment 5•4 years ago
|
||
I filed Bug 1677490 for better diagnostics in this area.
This file handles the injection, and the only way I know to debug it at this point is to do it locally on the machine:
https://searchfox.org/mozilla-central/source/devtools/client/performance-new/frame-script.js
Mayank: Could you please provide your OS information?
|
|
Reporter | |
Comment 6•4 years ago
|
||
|
|
Reporter | |
Comment 7•3 years ago
|
||
havent reproduced this for some time. Closing as fixed.
Description
•