Uploaded image for project: 'Realm Core'
  1. Realm Core
  2. RCORE-1613

Windows x86 bad allocs in tests

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      We have observed several instances of windows x86 test machine running out of memory:

      One instance:

      C:\jenkins\workspace\realm_realm-core_PR-6597\test\test_table.cpp:2498: ERROR in Table_AllocatorCapacityBug: Unhandled exception after line 2498 class std::bad_alloc: bad allocation

      Another:

      Thread[09]: C:\jenkins\workspace\realm_realm-core_PR-6557@2\test\test_array.cpp:1568: ERROR in Array_count: Unhandled exception after line 1601 class std::bad_alloc: bad allocation

      It is likely that this 32 bit machine is under a lot of memory pressure when several of our unit tests which request large amounts of memory happen to run concurrently. One way to fix this is to mark these tests as NONCONCURRENT_TEST.

            Assignee:
            Unassigned Unassigned
            Reporter:
            james.stone@mongodb.com James Stone
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: