Closed Quuxplusone closed 4 years ago
Attached browser_jumbo_15-e948b2.sh
(17883 bytes, application/x-shellscript): clang run script
UPDATE: Uploaded pre-processed source to my web space.
Well, std::bad_alloc just means you ran out of memory. There could be some runaway memory allocation, but it's much more likely just resource exhaustion. On Linux I can't observe any exceptions with your file, but there is around 1.3 GB of memory being allocated with Clang 6. With multiple compile jobs running at the same time it's not unreasonable to run out of memory then.
As a practical advice: reduce the number of concurrent compile jobs or just try again.
Maybe the error reporting could be improved here. Maybe we shouldn't suggest filing a bug report if we have an uncaught exception (though by default LLVM is compiled without exception support) of type std::bad_alloc, and instead point to the likely reason of resource exhaustion.
So I'm assigning this to the driver component, but since -fexceptions is not the default they might decide not to anything about this.
browser_jumbo_15-e948b2.sh
(17883 bytes, application/x-shellscript)