-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.2.0-rc4
-
Component/s: JavaScript
-
None
-
Fully Compatible
-
ALL
-
Platform D (12/11/15)
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.
- depends on
-
SERVER-21728 Disable extra threads for JSRuntimes
- Closed
- is depended on by
-
SERVER-21709 Map Reduce causes segfault in 3.2 RC4
- Closed