From a9ca2137aa3ebcf9cf094b20cf30cf50ba577892 Mon Sep 17 00:00:00 2001 From: Austin Clements Date: Thu, 12 Nov 2015 12:24:36 -0500 Subject: [PATCH] test: really force heap profile update in heapsampling.go The heap profile is only guaranteed to be up-to-date after two GC cycles, so force two GCs instead of just one. Updates #13098. Change-Id: I4fb9287b698f4a3b90b8af9fc6a2efb3b082bfe5 Reviewed-on: https://go-review.googlesource.com/16848 Reviewed-by: Dmitry Vyukov --- test/heapsampling.go | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/heapsampling.go b/test/heapsampling.go index ed9208c1f42..c00b866680a 100644 --- a/test/heapsampling.go +++ b/test/heapsampling.go @@ -92,6 +92,9 @@ func checkValue(fname string, ln int, name string, want, got int64) { func getMemProfileRecords() []runtime.MemProfileRecord { // Force the runtime to update the object and byte counts. + // This can take up to two GC cycles to get a complete + // snapshot of the current point in time. + runtime.GC() runtime.GC() // Find out how many records there are (MemProfile(nil, true)),