Comment 35 for bug 1642068

If it never stops growing, it's obviously a leak.. somewhere! If it stabilizes after a while, then it's a side effect of Go being a non-deterministic garbage collected language. Again, data.

If the goal is testing this particular code path, it'd be best to have a tiny test case exercising it, rather than doing something like "snap find".