Comments
Sort by recent activity
We've been working on a large .Net set of applications that deals with very large data sets for almost 5 years now.
Every single memory issue we've run into (and we've had many) has been related to large heap fragmentation. What often looks like a leak is due to the large heap getting fragmented.
Every time the solution has been to allocate large pools of memory up front and manage reuse ourselves.
Once we do that "leaks" magically go away.
It sure would be nice to have a tool to help identify these sections of code.
Sometimes a "leak" finding tool helps but it's quite looking for the root of the problem but rather at the symptom. / comments
We've been working on a large .Net set of applications that deals with very large data sets for almost 5 years now.
Every single memory issue we've run into (and we've had many) has been related to...