]> Cypherpunks repositories - gostls13.git/commit
[release-branch.go1.14] doc/articles/race_detector: mention memory leak potential
authorKevin Burke <kev@inburke.com>
Mon, 24 Feb 2020 04:45:51 +0000 (20:45 -0800)
committerDmitri Shuralyov <dmitshur@golang.org>
Tue, 25 Feb 2020 23:52:57 +0000 (23:52 +0000)
commit99f8de733936785d0e5c0d1271539d3f2f26d009
treeaba701bb7317d48844f58e930a8f89c965dc91f5
parent3dcb516d425989a8916188abbb36fe1ac386a54f
[release-branch.go1.14] doc/articles/race_detector: mention memory leak potential

As far as I can tell, there is no public documentation on this topic,
which cost me several days of debugging.

I am possibly unusual in that I run binaries in production with the
race detector turned on, but I think that others who do the same may
want to be aware of the risk.

Updates #26813.
Updates #37233.

Change-Id: I1f8111bd01d0000596e6057b7cb5ed017d5dc655
Reviewed-on: https://go-review.googlesource.com/c/go/+/220586
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
(cherry picked from commit ba093c4562e7464e95a4bde6505d270b71ed623f)
Reviewed-on: https://go-review.googlesource.com/c/go/+/221019
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
doc/articles/race_detector.html