Add reporter for loaded JSMs
Categories
(Core :: XPConnect, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox87 | --- | fixed |
People
(Reporter: mccr8, Assigned: kmag)
Details
Attachments
(1 file)
It would be nice to tell at a glance in a memory report which JSMs are loaded.
| Reporter | ||
Comment 1•5 years ago
|
||
It would also make it easier to tell if some change caused an additional JSM to be loaded.
This would be an "other measurements" reporter that would iterate over the set of loaded modules from somewhere in mozJSComponentLoader.
| Assignee | ||
Comment 2•5 years ago
|
||
Note we already have a list of these in Cu.loadedModules for the sake of the startup performance mochitests.
| Reporter | ||
Comment 4•5 years ago
|
||
This would be a good introductory bug for somebody who wants to become more familiar with our JSM loading (should such a person exist).
| Assignee | ||
Comment 5•5 years ago
|
||
This makes it much easier to determine which modules and components are loaded
in which processes now that they no longer each have their own compartments.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:kmag, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 8•4 years ago
|
||
Backed out changeset 748d8c28435d (Bug 1662846) for mochitest failures at test_memoryReporters.xhtml
https://hg.mozilla.org/integration/autoland/rev/22360273336512474a9aaf82b55794a5960d1be6
Push with failures:
https://treeherder.mozilla.org/jobs?repo=autoland&revision=748d8c28435d2f022a78bf1b26d6f060afe4e2e1&selectedTaskRun=Sr1vqH84Swm59-wvFnOrsg.0
Failure log:
https://treeherder.mozilla.org/logviewer?job_id=326233255&repo=autoland&lineNumber=111627
| Assignee | ||
Updated•4 years ago
|
Comment 10•4 years ago
|
||
| bugherder | ||
Description
•