-
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)
We should abort in out of memory conditions by setting the out of memory status on the scope and requesting an interrupt, rather than relying on spidermonkey always handling out of memory conditions gracefully.
While spidermonkey can handle most cases, by gcing and coming up with enough memory to fail out gracefully, there are edge cases where it can't. We shouldn't crash for any of those.