Date: Sat, 08 Feb 2020 16:33:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241848] lib/googletest/gtest/tests: gmock-matchers_test.cc requires a pathological amount of memory to compile Message-ID: <bug-241848-227-MRXWIkMjz7@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241848-227@https.bugs.freebsd.org/bugzilla/> References: <bug-241848-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241848 --- Comment #9 from Robert Clausecker <fuz@fuz.su> --- In reply to comment #5 of Mark: That was a -j1 world build with swap enabled. On a separate SSH session, I watched the clang process spike to 1.5 GB (with some 700 MB resident, not s= ure) before it got killed. I was eventually able to get the compilation to run through by temporarily configuring extra swap space but it was a real pain = to do. Please though: I am extremely sure this is a compiler bug or poorly designed program, not a configuration issue. Tweaking VM settings will not solve the underlying issue which is probably a memory leak or something. And if peop= le have to perform arcane tweaks to be able to upgrade their system at all (as= no other upgrade path than upgrading from source is supported on ARM32), that's really bad news for people who actually want to run FreeBSD on their ARM bo= xes. Please solve the underlying issue. I want a solution, not a bandaid. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241848-227-MRXWIkMjz7>