-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: JavaScript
-
None
-
ALL
Once you get an "out of memory" error, the JavaScript runtime becomes unusable.
// Add this to system.js
{ "id" : "f1", "value" : function cf2f {
a = [];
b = [];
c = [];
for (i = 0; i < n; i++)
} }
// Then execute this:
> db.eval("f1(10)")
null
> db.eval("f1(10000)")
null
> db.eval("f1(100000)")
null
> db.eval("f1(1000000)")
Thu Apr 28 11:21:45 uncaught exception: {
"errno" : -3,
"errmsg" : "invoke failed: JS Error: out of memory nofile_b:6",
"ok" : 0
}
> db.eval("f1(10)")
Thu Apr 28 11:21:49 uncaught exception: {
"errno" : -3,
"errmsg" : "invoke failed: JS Error: out of memory nofile_b:1",
"ok" : 0
}
- depends on
-
SERVER-3656 increase spidermonkey JS heap limit to 64MB
- Closed
- is depended on by
-
SERVER-4107 Server exits after JS Error: out of memory nofile_b:7
- Closed