[llvm-bugs] [Bug 49823] New: Compiler hits OOM failure

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=49823

            Bug ID: 49823
           Summary: Compiler hits OOM failure
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: brucedawson at chromium.org
                CC: blitzrakete at gmail.com, dgregor at apple.com,
                    erik.pilkington at gmail.com, llvm-bugs at lists.llvm.org,
                    richard-llvm at metafoo.co.uk

While compiling an in-progress version of a bug fix the compiler went into a
memory allocation loop and hit an OOM failure. When I reproduced the bug by
rebuilding the problematic target I saw the memory usage hit 20 GB before I got
bored of watching and killed it.

The Chromium CL which triggers this bug is uploaded at crrev.com/c/2803616

Supporting information from process_crashreports.py can be found here:

gs://chrome-clang-crash-reports/v1/2021/04/02/user-brucedawson-clipboard_win-3750a6.tgz

-- 
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/20210402/c6368dd2/attachment.html>