Info

Since we added the jsHeapLimitMB setParameter, it's possible to make the javascript engine run out of memory before it is able to initialize a JSContext. Because the OOM handling of our custom allocator needs a pointer to the scope to mark it as OOM, this can cause the server to abort. We need to make sure the server doesn't crash when this happens and issue an appropriate warning that the jsHeapLimitMB is too low to actually run any javascript.

Top User Comments

xgen-internal-githook commented on Mon, 17 Oct 2016 15:19:21 +0000: Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'} Message: SERVER-26596 Make sure test doesn't break other tests and fix memory leak Branch: master https://github.com/mongodb/mongo/commit/40c24abaa05450c612f00209b81d63d3c6acd35b xgen-internal-githook commented on Thu, 13 Oct 2016 14:52:10 +0000: Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'} Message: SERVER-26596 Don't abort when javascript heap limit is set too low to initialize spidermonkey Branch: master https://github.com/mongodb/mongo/commit/0344a7542f9318730cce289fe143295f6f99b4f8

Steps to Reproduce