Dear all,
I created a windows forms application using LINQ to connect to an Microsoft SQL Server 2008. The database is acessed appr. every 5 seconds. By using an profiler (and even the task manager after some time) it's clear that my application has an strong raising memory leak. The result of the profiler was, that objects created by LINQ were not disposed. After a runtime of an couple of hours the used memory was about 100 MB which is far far to much for such a small application.
After some research I put the LINQ connection into an using block but without any effect.
Is this a bug within LINQ or do I make an mistake in using LINQ?
If requested I will post the source code next time.
Thanks in advance.
Best Regards
Gerd Blake
Loading
Matt KlassenPosted Jun 25, 2009, 3:52 PM
I've made sure I'm closing and disposing the data context (DataContext.Connection.Close()/.Dispose()), but even that doesn't seem to make any difference, and after 24 hours my little app is up to hundreds of MB of RAM.
Any help?