Closed
Bug 710504
Opened 13 years ago
Closed 12 years ago
Provide a way to drop memory that doesn't require allocating memory
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: n.nethercote, Unassigned)
Details
(Whiteboard: [MemShrink:P2])
On memory pressure, the JS engine does a GC, which as well as cleaning up the heap drops various other things like JIT code. It would be nice if we could drop things without having to do the GC, because doing a GC can require us to allocate memory before any is dropped.
For the most part, the JS engine should not allocate memory during a GC. I know of one place where we remove elements from hashtables, which can cause memory allocation. But generally we try to allocate everything up front. CC may be different.
Comment 2•13 years ago
|
||
The CC allocates a ton of memory.
Reporter | ||
Updated•13 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Reporter | ||
Updated•12 years ago
|
Assignee: n.nethercote → general
Reporter | ||
Comment 3•12 years ago
|
||
Eh, doesn't seem that important now.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•