Add a profiler preset for necko
Categories
(DevTools :: Performance Tools (Profiler/Timeline), task, P3)
Tracking
(firefox96 fixed)
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
Details
Attachments
(1 file)
The default presets don't profile the threads we normally care about in networking bugs (DNS, SocketTransportThread, StreamTransportThread, etc).
Comment 1•4 years ago
|
||
This is where the presets are defined: https://searchfox.org/mozilla-central/rev/3c8a7970944daaf917b547dffc0790bcd37cadc1/devtools/client/performance-new/popup/background.jsm.js#100
Feel free to add a preset there :-) It may be a good idea to wait a few days though, because Florian is currently changing the existing presets a bit.
Updated•4 years ago
|
| Assignee | ||
Comment 2•4 years ago
|
||
Thanks. I'll give it a few days.
Comment 3•4 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #1)
It may be a good idea to wait a few days though, because Florian is currently changing the existing presets a bit.
Doing this in bug 1741235.
Comment 4•4 years ago
|
||
The profiler already supports recording MOZ_LOG's as markers by including "profilermarkers" in the MOZ_LOG env var value.
It would be cool figure out whether we can include this either by default or as an option when capturing profiles with this networking preset.
| Assignee | ||
Comment 5•4 years ago
|
||
Comment 7•4 years ago
|
||
Backed out for causing browser-chrome failures in browser_xpcom_graph_wait
Backout link: https://hg.mozilla.org/integration/autoland/rev/ea1661d1c9a86ae325ae4139255f01379dba7012
INFO - TEST-PASS | toolkit/components/backgroundtasks/tests/browser/browser_xpcom_graph_wait.js | resource://testing-common is not substituted - true == true -
[task 2021-12-01T06:27:25.489Z] 06:27:25 INFO - Buffered messages finished
[task 2021-12-01T06:27:25.489Z] 06:27:25 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/backgroundtasks/tests/browser/browser_xpcom_graph_wait.js | 0 == -11 - JS frame :: chrome://mochitests/content/browser/toolkit/components/backgroundtasks/tests/browser/browser_xpcom_graph_wait.js :: test_xpcom_graph_wait :: line 216
[task 2021-12-01T06:27:25.489Z] 06:27:25 INFO - Stack trace:
[task 2021-12-01T06:27:25.489Z] 06:27:25 INFO - chrome://mochitests/content/browser/toolkit/components/backgroundtasks/tests/browser/browser_xpcom_graph_wait.js:test_xpcom_graph_wait:216
[task 2021-12-01T06:27:25.493Z] 06:27:25 INFO - Not taking screenshot here: see the one that was previously logged
| Assignee | ||
Comment 8•4 years ago
|
||
It seems to be caused by the inclusion of the cache i/o thread in the other patch.
With only this patch there is no failure. https://treeherder.mozilla.org/jobs?repo=try&revision=8485d53ab76f1f404662b06ec7472dac3e5c2ed0
Comment 10•4 years ago
|
||
| bugherder | ||
Description
•