Databases
StackOverflow2013
Postsdbo
POStrange memory leak related to DataContext and PropertyChanged event
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStrange memory leak related to DataContext and PropertyChanged event
    primarykey
    data
    text
    <p>I have a windows service written in C#. </p> <p>After running for a couple of days it will be using about 2GB of ram.</p> <p>Using ".NET Memory Profiler" I noticed that there is a hugely increasing number of instances of a certain T_TurbineEventLog class. These objects come from a loop that fetches them every minute through a LINQ-to-SQL query (lots of them each time), and on certain occations I keep a reference to few of them.</p> <p>The memory profiler told me that most of these objects are only kept alive through a shortest root path resembling the following (from my memory):</p> <blockquote> <p>root -> ... -> T_TurbineEventLog -> PropertyChanged -> ...(eventhandlers) -> IdentityManager -> ...Cache -> T_TurbineEventLog[] -> T_TurbineEventLog.</p> </blockquote> <p>Thus, to me it seems that the few T_TurbineEventLog objects that I keep live myself for good reasons hold an indirect link to the totality of original SQL Query results through an event handler (keep in mind that the above shows the <em>shortest</em> root path). </p> <p>I read the objects inside a small <code>using (var db=new MyDataContext...)</code>, so I guess the datacontext ought to unsubscribe from the PropertyChanging event, but for some reason hasn't.</p> <p>I have google'd to the best of my abilities but this doesn't seem like a known problem. So what can I be doing wrong?</p> <p>The solution so far has been to set <code>ObjectTrackingEnabled=false</code>, which actually removes the leak.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBjarke Ebert
    1. USBjarke Ebert
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POStrange memory leak related to DataContext and PropertyChanged event
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt looks like your solution to set `ObjectTrackingEnabled = false` is the best solution. Realize that the context keeps a hold of all objects that it fetches so that it can watch for changes. Just disposing it doesn't remove the event hooks on INotifyPropertyChanged/INotifyPropertyChanging thus they are retained longer than they should be. Since you don't need the change tracking, removing it should not only fix your memory leak, but improve performance as well.
      singulars
      1. POStrange memory leak related to DataContext and PropertyChanged event
      1. USJim Wooley
    2. COI have also seen this scenrio exactly how you describe it. In my situation I had to go through a few places where a small "using" statement was used to work with the datacontext, and use the ObjectTracking=false option. I was using Ants profiler and saw the number of instances of a particular class within the datacontext continually climb.
      singulars
      1. POStrange memory leak related to DataContext and PropertyChanged event
      1. USGlav
    3. COAre you using the entities outside of the using(...) scope in which the DataContext is declared? Just because you kill off the data context, references to other things may exist. If you are using the entities outside the data context scope, you need to create non-LINQ / POCO classes that mirror the data model and deep copy into these. If you want examples, I can provide them.
      singulars
      1. POStrange memory leak related to DataContext and PropertyChanged event
      1. USDaniel P. Bullington
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload