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

Force SpiderMonkey to garbage collect in ReplSetTest.checkOplogs

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0, 4.2.13, 4.4.5, 4.0.24
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Repl 2021-02-08
    • 7

      Certain tests, like the backup_restore_*.js tests, set a large oplog size. If the oplog becomes large (especially if there is a concentration of particularly large entries), SpiderMonkey can cause an OOM when checking the oplogs. This should be able to be fixed by manually having SpiderMonkey garbage collect (at least if the oplog is large), which is what the itcount function currently does to avoid this issue.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: