Closed
Bug 1131405
Opened 10 years ago
Closed 10 years ago
GC more aggressively when we're out of memory
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
mozilla38
| Tracking | Status | |
|---|---|---|
| firefox38 | --- | fixed |
People
(Reporter: terrence, Assigned: terrence)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
patch
|
sfink
:
review+
|
Details | Diff | Splinter Review |
Currently this does a single-zone, non-shrinking GC. It seems that if we need to GC work anyway and we're actually out of memory, we should probably do an all-zones, shrinking GC to get as much memory back as possible.
|
Assignee | |
Comment 1•10 years ago
|
||
Attachment #8561797 -
Flags: review?(sphink)
|
|
Assignee | |
Updated•10 years ago
|
Target Milestone: flash10 → ---
|
||
Updated•10 years ago
|
Attachment #8561797 -
Flags: review?(sphink) → review+
|
|
Assignee | |
Comment 2•10 years ago
|
||
Note, this change was pulled out of Part 2 from this green try run, so we should be gtg:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=254ffde43bb4
https://hg.mozilla.org/integration/mozilla-inbound/rev/de7c130a0d58
|
||
Comment 3•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
You need to log in
before you can comment on or make changes to this bug.
Description
•