From owner-freebsd-bugs@freebsd.org Wed Feb 26 03:55:02 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 08492249E78 for ; Wed, 26 Feb 2020 03:55:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48S24j4z6Fz4Mn0 for ; Wed, 26 Feb 2020 03:55:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 56EAD249E77; Wed, 26 Feb 2020 03:55:01 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5454B249E76 for ; Wed, 26 Feb 2020 03:55:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48S24j0S3Yz4MlX for ; Wed, 26 Feb 2020 03:55:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8FCAD2160A for ; Wed, 26 Feb 2020 03:55:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 01Q3t0HV098106 for ; Wed, 26 Feb 2020 03:55:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 01Q3t00L098105 for bugs@FreeBSD.org; Wed, 26 Feb 2020 03:55:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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 Date: Wed, 26 Feb 2020 03:55:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 03:55:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241848 --- Comment #12 from Mark Millard --- Just to add to the examples of what it takes to build and link gmock-matchers_test . . . In /usr/src/lib/googletest/gmock_main/tests/ I tried building gmock-matchers_test on an Orange Pi+ 2ed (armv7 Cortex-A7 with 2 GiBytes of RAM and 1740Mi swap/paging space). The context is head -r358132 . I use a modified version of top that keeps track of its sampled "Max. Observed Active" (MaxObsActive), MaxObsWired, MaxObs(Act+Wir), and, for swap use, MaxObsUsed (if any). It is also biased to present more digits (smaller unit size) and be explicit about powers of 2 factors being in use for memory size display. After finishing in somewhat over 20 minutes (under 25?), the odd variant of top was showing: 1019Mi MaxObsActive, 193444Ki MaxObsWired, 1146Mi MaxObs(Act+Wir) Swap: 1740Mi Total, 1740Mi Free That spans the link as well. So swap/paging space was not observed to be used --but clearly would have been on a 1 GiByte machine. Similarly Free RAM was never observed to be low but would have been on a 1 GiByte machine. An example aarch64 is a Rock64 (not Pro) with 4 GiBytes of RAM: 1753Mi MaxObsActive, 633084Ki MaxObsWired, 2368Mi MaxObs(Act+Wir) Swap: 4608Mi Total, 4608Mi Free (It shows a lot more Wired even without the build, just because of the larger amount of RAM.) So, even just looking at the MaxObsActive, it indicates that a 1 GiByte RAM machine would be paging/swaping and a 2 GiByte machine would likely do some as well (far less). There is a significant MaxObsActive difference between the armv7 and aarch64 contexts. But it would be interesting to see what a 2 GiByte aarch64 would be like. --=20 You are receiving this mail because: You are the assignee for the bug.=