[SERVER-21717] We should soft abort on out of memory conditions in javascript Created: 01/Dec/15  Updated: 03/Dec/15  Resolved: 02/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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platform D (12/11/15)
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 02/Dec/15 ]

Author:

{u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}

Message: SERVER-21717 Be more graceful in JS OOM

rather than return null to spidermonkey, just request that we bail out
as soon as possible.
Branch: master
https://github.com/mongodb/mongo/commit/addf42317b9e9a88d22dad86470b206c25d2ea5f

Generated at Thu Feb 08 03:58:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.