Date: Fri, 07 Feb 2020 19:41:53 +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-WrG2HJEhTc@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 #5 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Dave Evans from comment #1) Was this a -j1 build? Something larger? (There could be other things worth reporting about the build context.) It can be interesting to watch the system with top sorted by resident RAM use (decreasing). It can give a clue what are the major things contributing to low free RAM while watching. I'm not sure one can infer much from which process FreeBSD decides to kill. Other evidence is likely better about what is contributing to the sustained low free RAM that likely is what leaded to the process kill(s). To Robert: I've been replying mostly to Dave because it has been a significant time since I've experimented with a 1 GiByte machine for buildworld buildkernel and the like. Dave indicated over 2 GiByte for his context. You could try vm.pageout_oom_seq=3D1200 and a -j1 build and see if it helps you. Reporting the result here might be useful. Actually, you indicated "upgrade to FreeBSD 12.1", so your context is appearently older, such as 12.0. I'm not sure if vm.pageout_oom_seq goes back that far. That might leave you only with -j1 (which, for all I know, you might have already been using). --=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-WrG2HJEhTc>