Diagnosing memory leaks with native leaks.

[mikelle-rogers]

Walkthrough: see #515

[mikem8361]

Not sure we need to document how to debug native leaks.

[noahfalk]

I'll take it and figure out what to do with it.

[noahfalk]

I've been thinking on this one a bit and I think we should mark this enhancement and move it to the Future milestone. While I don't doubt some users of .NET would appreciate a guide on diagnosing native memory leaks, I am only aware of about ~4 cases over the past 4 years. There are also a variety of pre-existing web articles and the methods to diagnose these issues vary based on OS and C runtime implementation. In total I expect we'd have to spend a non-trivial effort to research and write something substantial enough that it would be an improvement over users just doing a web search with the particulars of their issue and environment. It doesn't feel like a good return on our time unless we got a lot more feedback that native leaks are an important pain point.

Thoughts?

[mikelle-rogers]

I've been thinking on this one a bit and I think we should mark this enhancement and move it to the Future milestone. While I don't doubt some users of .NET would appreciate a guide on diagnosing native memory leaks, I am only aware of about ~4 cases over the past 4 years. There are also a variety of pre-existing web articles and the methods to diagnose these issues vary based on OS and C runtime implementation. In total I expect we'd have to spend a non-trivial effort to research and write something substantial enough that it would be an improvement over users just doing a web search with the particulars of their issue and environment. It doesn't feel like a good return on our time unless we got a lot more feedback that native leaks are an important pain point.

Thoughts?

That sounds good to me.

[jerviscui]

I'd like to see it.

[botinko]

I'd like to see it.