Open
Bug 1357435
Opened 7 years ago
Updated 2 years ago
Asynchronously free executable memory when garbage collecting
Categories
(Core :: JavaScript: GC, enhancement, P3)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: djvj, Unassigned)
Details
(Keywords: triage-deferred)
We seem to free ExecutablePool memory synchronously when discarding jitcode during garbage collection. This seems to invoke a lot of mprotect() calls when discarding jitcode, which should be avoided during GCs to save time. We should push as much of the jitcode free logic as possible to deferred (preferably off-main-thread) free code.
Comment 1•7 years ago
|
||
Sometimes we do last-ditch GCs to free up executable code, see eg bug 1356631 and bug 1338217 for background. In that case, freeing doesn't have to happen during GC but it must happen synchronously thereafter.
Updated•7 years ago
|
Keywords: triage-deferred
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•