Add memory reporter for HelperThreads::helperContexts_
Categories
(Core :: JavaScript Engine, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
This is a list of JSContexts. It uses about 30,000 bytes of memory in an empty content process. We should have a memory reporter for them.
Assignee | ||
Comment 1•5 years ago
|
||
My patch hits a protected data assert. Maybe due to JSContext::SizeOfExcludingThis calling cycleDetectorVector() while the context isn't active.
Comment 2•5 years ago
|
||
For what it's worth, we could easily initialize this more lazily. Most helper thread tasks don't request a JSContext anymore.
We have parsing (will be fixed short-term-ish after Stencil) and some GC tasks. On the other hand, if we can remove this completely later this year maybe we should just wait for that.
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
(In reply to Jan de Mooij [:jandem] from comment #2)
For what it's worth, we could easily initialize this more lazily. Most helper thread tasks don't request a JSContext anymore.
Thanks, that's an interesting idea. I filed bug 1643368 for it.
Assignee | ||
Comment 4•5 years ago
|
||
With the new regexp reporter, this is 41,600 bytes of memory in a nearly-empty content process.
Assignee | ||
Comment 5•5 years ago
|
||
JSContexts aren't stored inline, so having this helper is convenient.
Assignee | ||
Comment 6•5 years ago
|
||
This is 41600 bytes of unreported memory in each process.
Comment 8•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/07fff448894b
https://hg.mozilla.org/mozilla-central/rev/57cbb3edaf8e
Description
•