Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-26596

Javascript allocator should not abort when OOM during JSContext creation

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.0-rc1
    • None
    • Fully Compatible
    • ALL
    • Platforms 2016-10-31
    • 0

    Description

      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.

      Attachments

        Activity

          People

            jonathan.reams@mongodb.com Jonathan Reams
            jonathan.reams@mongodb.com Jonathan Reams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: