Databases
StackOverflow2013
Postsdbo
POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
    primarykey
    data
    text
    <p>In my application, I have some user controls that open in the main window. I suppose to open the user controls and close them. In each user control, I have pictures , textboxes and label like any information form. I noticed that memory doesn't reclaim by garbage collector.I have searched the internet for a weak to resolve memory leak of my application. I found some good answers to my question, but most of them related to .net framework 3.5 or earlier. I used memory profiler to find the clue based on some advises. When I used memory profiler, I found a lot weak references caused by binding to object. This is according with <a href="https://stackoverflow.com/questions/7737070/prevent-memory-leaks-in-wpf">link</a> and I tried to remove the binding just before removing parent control, and It didn't solve my problem. here xaml code:</p> <pre><code>&lt;TextBox x:Name="nameTextBox" Text="{Binding Name, Mode=TwoWay}" /&gt; </code></pre> <p>I Set DataContext to an instance of my Model. My model like follows</p> <pre><code> public class MyModel : INotifyPropertyChanged { private string name; public string Name { get { return name; } set { if (name!= value) { name= value; OnProperyChanged("Name"); } } } public event PropertyChangedEventHandler PropertyChanged; protected void OnProperyChanged(string propertyName) { if (PropertyChanged != null) this.PropertyChanged(this, new PropertyChangedEventArgs(propertyName)); }` ... } </code></pre> <p>I tried to clear my binding using following code:</p> <pre><code> BindingOperations.ClearBinding(nameTextBox,TextBox.TextProperty); </code></pre> <p>but weak reference didn't go away. I found a useful <a href="http://www.codeproject.com/Articles/29922/Weak-Events-in-C#heading0010" rel="nofollow noreferrer">code project page</a> , but it is for event handlers. At the end, if I misunderstand the links that I mentioned, Please give me a clue that what I have to do? If there is another solution for binding. </p> <p>Note: I have seen the <a href="https://stackoverflow.com/questions/18542940/wpf-can-bindings-create-memory-leaks">Link</a> and I know I have to get rid of following elements:</p> <ul> <li>Event handlers to objects in parent windows</li> <li>Registering to events from static objects</li> <li>Using timers</li> <li>Data binding</li> <li>Changing the Text property of a text box</li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAAAA
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou need to rename the title of your post. I'm pretty sure weak references by definition do not cause memory leaks
      singulars
      1. POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
      1. USMickyD
    2. COI used memory profiler and I didn't see any strong reference in the list.That is why mentioned "weak reference". After I submit this post, I actually suspected to Image reference which is very annoying during binding. I set my image's reference null when I want to close my control. I think that Image is reason that weak reference remains in memory.
      singulars
      1. POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
      1. USAAAA
    3. COI know title must be short. my title is not appropriate . any suggestion about title pleased me.
      singulars
      1. POWPF 4.5: how to remove weak reference caused by binding to an object in order to avoid memory leak
      1. USAAAA
 

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