I have been having some issues with LINQ-To-SQL around memory usage. I’m using it in a Windows Service to do some processing, and I’m looping through a large amount of data that I’m pulling back from the context. Yes – I know I could do this with a stored procedure but there are reasons why that would be a less than ideal solution.
Anyway, what I see basically is memory is not being released even after I call context.SubmitChanges(). So I end up having to do all sorts of weird things like only pull back 100 records at time, or create several contexts and have them all do separate tasks. If I keep the same DataContext and use it later for other calls, it just eats up more and more memory. Even if I call Clear() on the ‘var tableRows‘ array that the query returns to me, set it to null, and call SYstem.GC.Collect() – it still doesn’t release the memory.
Now I’ve read some about how you should use DataContexts quickly and dispose of them quickly, but it seems like their ought to be a way to force the context to dump all its data (or all its tracking data for a particular table) at a certain point to guarantee the memory is free.
Anyone know what steps guarantee that the memory is released?
If you don’t need object tracking set DataContext.ObjectTrackingEnabled to false. If you do need it, you can use reflection to call the internal DataContext.ClearCache(), although you have to be aware that since its internal, it’s subject to disappear in a future version of the framework. And as far as I can tell, the framework itself doesn’t use it but it does clear the object cache.