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

abort() in tcmalloc when allocated memory size is ridiculously large

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Security
    • None
    • Security 2021-05-31, Security 2021-06-14
    • 21

      In BF-20042 we was a memory corruption issue correlated with tcmalloc: large alloc 3761212780863488 bytes == (nil) @. Memory requested amounts to ~3.7 petabytes. A core dump followed during cache release. It is unclear, where does such large allocation originates, but it clearly is a bug.

      In order to make debugging simpler we must fail-fast when it happens, so that a core dump is produced and location of fault is easier to identify.

      For the purposes of this ticket, a code change should be limited in functionality to evergreen-only invocations by the use of environment variable.

            Assignee:
            sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
            Reporter:
            sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: