I somehow completely misunderstood that from the Go documentation when first reading it; thank you for clarifying that. There must have been some other leaking

I somehow completely misunderstood that from the Go documentation when first reading it; thank you for clarifying that. There must have been some other leaking going on. He was using a largish library when he saw the leak and eventual crash so maybe it was due to improper pooling or C api calls? I'll have to ask him more about it.