[SERVER-21716] SpiderMonkey doesn't appear capable of gc'ing objects created during the map phase Created: 01/Dec/15 Updated: 08/Dec/15 Resolved: 03/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 3.2.0-rc4 |
| Fix Version/s: | 3.2.0-rc6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Platform D (12/11/15) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Spidermonkey doesn't appear to be actually gc'ing memory during the map phase of map reduce. This doesn't affect map reduce jobs with less than 1.1 gigs of working set (we reap the context at the end of the job, which frees the memory), but oom's those over that amount. |
| Comments |
| Comment by Mira Carey [ 03/Dec/15 ] |
|
This was a consequence of ballooning in the js heap, and is fixed by |