HeaderedContentControl's content setting process increases memory usage (Memory Leak)

Question

4.50/5 (2 votes)

See more:

Hi,

HeaderedContentControl's content setting process increases memory usage (Memory Leak)

I am using HeaderedContentControl control in my WPF application.

and I have bound content property to view model property using Data binding.

XML

<HeaderedContentControl HorizontalContentAlignment="Center" FocusVisualStyle="{x:Null}"  Margin="20" Grid.Row="1" Grid.Column="0" Content="{Binding Path=CurrentPage}" />

Everytime it loads page in it, increases memory size.

I would like to know, what's happening here. Why it increases memory size everytime I load a page in it.

Thanks in advance :)

Posted 28-Jun-11 22:01pm

Sanjay J Patolia

Updated 28-Jun-11 22:16pm

Tarun.K.S

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 29-Jun-11 4:09am

OK, memory size, but what makes you feel a leak? Don't get me wrong, leaks are possible even on a managed platform. But how do you know?
--SA

Sanjay J Patolia 29-Jun-11 4:12am

When I click on next button to load a next page in it. This causes memory size increase. everytime I click on next or previous button and every move will load a specific page in a HeaderedContentControl. I meant to say that if it has been loaded once and I click on next or previous it should just give a reference or some. but it increases memory size evrytime.

Sanjay J Patolia 29-Jun-11 4:14am

Is above process an inbuild behaviour or what I am not getting it!!!

Mark Salsbery 29-Jun-11 17:19pm

.NET will gleefully keep allocating memory if it's available until it decides to free some up. Like others have asked, how do you know it's a leak?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Answer 1 · 2011-06-28T22:14:00

Solution 1

Without seeing your code, it's difficult to say, but I have a suspicion that the problem is probably event handler leaks (they are the commonest cause of leaks in .NET). Make sure that you are deallocating any event handlers that you have allocated before you leave the page.

Posted 28-Jun-11 22:14pm

Pete O'Hanlon

Comments

Sanjay J Patolia 29-Jun-11 4:27am

Well I have verified with event handlers it does not create the leak here. May be something else.

Pete O'Hanlon 29-Jun-11 4:49am

Again, without seeing your code it's hard to verify. Sorry about that.