[LLVMbugs] [Bug 22026] New: LargeMmapAllocator crashes the process on OOM even if allocator_may_return_null=1

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=22026

            Bug ID: 22026
           Summary: LargeMmapAllocator crashes the process on OOM even if
                    allocator_may_return_null=1
           Product: compiler-rt
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: compiler-rt
          Assignee: unassignedbugs at nondot.org
          Reporter: timurrrr at google.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

This hits us on Chromium on Win32 (32-bit):
[ RUN      ] DiscardableMemoryTests/DiscardableMemoryTest.AddressSpace/0
==8508==ERROR: AddressSanitizer failed to allocate 0x408000 (4227072) bytes of
LargeMmapAllocator (error code: 8)
==8508==AddressSanitizer CHECK failed:
D:\src\chr_trunk\src\third_party\llvm\projects\compiler-rt\lib\sanitizer_common\sanitizer_win.cc:89
"(("unable to mmap" && 0)) != (0)" (0x0, 0x0)

Looking at the LargeMmapAllocator code, it unconditionally does MmapOrDie, so
this is not OOM-friendly.
It's likely we haven't seen this earlier because it's much harder to OOM on x64
:)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20141224/f194589a/attachment.html>