WPF Increasing memory usage in time

Question

1.00/5 (2 votes)

See more:

, +

Hi all,

I'm creating a WPF program for kiosk in full screen running 12 hours/day every day. I have test in my home for memory usage since sometimes it becomes lag and slow. I run the program with task manager on top of the screen and start clicking the function on the screen. I see the memory increase when going to another page.

Every navigation will increase at least 50MB and most consume when next page is displaying a list of images. When timeout arrive and navigating back to home page, the memory still not decrease. I wonder why the memory is increasing.

Does WPF application not release the memory usage after going to another page?

If this still continue for a few hours, the program will crash.

How to encounter this problem actually?

I'm using WPF Application with Page (not WIndow)

Hoping for guide and help

EDITED: MEMORY PROFILER SUMMARY
Profiler Link

What is been used by the bytes(not very sure details)
http://postimg.org/image/7esumzjq5/[^]

Posted 14-Dec-15 6:34am

Luiey Ichigo

Updated 15-Dec-15 2:41am

v3

Add a Solution

Comments

CHill60 14-Dec-15 12:57pm

We can't see your screen or HDD nor read your mind - we'll need to see some code to help

Dave Kreskowiak 14-Dec-15 13:02pm

First, do NOT use Task Manager to see how much memory your application is actually using. The .NET CLR RESERVES memory for your application even though your app isn't using it. This is what Task Manager is showing you. Use PerfMon and the .NET Memory counters to see how much memory your app is actually using.

Sergey Alexandrovich Kryukov 14-Dec-15 15:00pm

5!—SA

Luiey Ichigo 14-Dec-15 21:35pm

Hi, thanks for recommendation. I see the task manager because pc is hang and when I see the memory use for my application is around 200MB. I'm now try to inspect using memory profiler but I dont know how to read the snapshot. I will update back the image

4 solutions

Solution 4

Be Careful from the accepted solution !

because ( SetProcessWorkingSetSize ) can have some serious negative side effects such as :

It can cause a significant performance hit. When the working set is trimmed, any subsequent memory accesses will result in page faults, which are expensive in terms of CPU time.
It doesn't actually reduce the amount of memory used by the process. It only affects the physical memory (RAM) usage, not the virtual memory usage. If your application has a memory leak, it will continue to consume more and more virtual memory over time.

Better Solutions

The best solution to a memory leak is to find and fix the source of the leak. This could involve:

Using a memory profiler to identify which objects are being held in memory and what is referencing them.
Reviewing your code to ensure that all resources are being properly disposed of, and that all event handlers are being unregistered when they're no longer needed.
Checking for common sources of memory leaks in WPF applications, such as static event handlers, data bindings that create strong references, and not unloading user controls when they're no longer needed.

Posted 31-May-24 21:07pm

Sam-SM

Updated 31-May-24 21:08pm

v2

Comments

Pete O'Hanlon 1-Jun-24 5:43am

Why have you hunted out a 9 year old question to answer?

Sam-SM 2-Jun-24 0:01am

As long as it's still appearing on google search, new developers may use the solution provided here not knowing the problems that it can cause them. I had to provide a better explanation so they learn the right way.

So now the better question is: why is that a problem for you?
Did I write that on top of your forehead?
Or it's painful to see someone trying to help people?

Solution 1

Memory Usage of the application is determined by our coding practices. Without seeing your code, we can't find out the reason for your issue. Anyway, following best programming practices will help you to develop memory efficient applications. Refer the following CP article,
1. Building High Performance WPF/E Enterprise Class Application in C# 4.5[^]
2. WPF / MVVM Real-Time Trading Application[^]

Posted 14-Dec-15 16:34pm

VR Karthikeyan

Comments

Luiey Ichigo 14-Dec-15 22:56pm

I want to post my code but which part, that I dont know where to start. Since every navigation to other page will increase the memory usage. When navigating back to home screen, its still stay at last memory usage. If navigate again, then it will increase more

VR Karthikeyan 15-Dec-15 1:35am

In this case, please refer the above specified articles, and use those best practices in your code.

johannesnestler 15-Dec-15 10:56am

no answer but chances are high you do something wrong: somethings come to my mind you can look for:
* Did you use strong (normal) references where you should have used WeakReference?
* Do you subscribe to handle events of long living objects (the Provider will hold a reference to every subscriber) wich then can't be GCed (may be solved by unsubscribing if handler is not needed any more)
* Do you load other resources on each Navigation which are then refernced by other parts of the System (maybe a static "global" property or something)
* Do you use any unmanaged "things" which may leak memory?

Luiey Ichigo 22-Dec-15 21:23pm

Hi johan,
1) What mean by strong/weak reference?
2) Every event is using within single page only. Not sharing and be used by another page. When the page is unloaded, I will empty every variable that been declared and use from the page e.g. Screen Timer, BackgroundWorker, Byte().
3) I load every DynamicResource from ResourceDictionary page. All page have same button/control for some function e.g. Continue, Back, Next, Previous.
4) On timer timeout, the page will navigate back to home page. At new instance of the page, I will clear all global variable/declaration e.g Structure, Arraylist.

Solution 2

OK, so you've got about 273MB worth of stuff sitting in byte arrays. What are they and what are you doing with them?

We can't see you're code so it's impossible to tell you what's going on.

Posted 14-Dec-15 17:19pm

Dave Kreskowiak

Comments

Luiey Ichigo 15-Dec-15 0:09am

The byte that im holding contains image of each ID. I will store the ID and image to arraylist and stream each byte to imagebrush on program. Is it mean that after I'm navigating to other page, the arraylist is not release as nothing?

Dave Kreskowiak 15-Dec-15 15:28pm

I can't see your code so it's impossible to say. You should really understand variable scope and the debugger to figure out what's going on.

If it's climbing every time you leave a page and go back, I'd say that you're adding/duplicating data into these structures when you don't have to.

Add a Solution

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

Jitesh Hirani · Accepted Answer · 2016-01-10T19:13:00

Hii Luiey Ichigo,
I have also developed POS application and WPF many times consumes much memory even when idle.
Even by following the above links(Provided in Solution 1),sometime a part of memory is not cleared(i.e. memory leak remains).
Please find the code below and use it in some common space like where window is unloaded.
This will remove your much part of Memory but will not clear Memory Leak left by your code(like this will not remove your event handlers if you have not unregistered them but if you open report viewer and call this code after closing report viewer you may find the difference).

Declare this

C#

[DllImport("KERNEL32.DLL", EntryPoint = "SetProcessWorkingSetSize", SetLastError = true, CallingConvention = CallingConvention.StdCall)]
       internal static extern bool SetProcessWorkingSetSize(IntPtr pProcess, int dwMinimumWorkingSetSize, int dwMaximumWorkingSetSize);

       [DllImport("KERNEL32.DLL", EntryPoint = "GetCurrentProcess", SetLastError = true, CallingConvention = CallingConvention.StdCall)]
       internal static extern IntPtr GetCurrentProcess();

Consume this code

C#

IntPtr pHandle = GetCurrentProcess();
            SetProcessWorkingSetSize(pHandle, -1, -1);

Please mark this as answer if your prblem is solved.
Thanks!!!

WPF Increasing memory usage in time

4 solutions

Solution 3

Solution 4

Solution 1

Solution 2

Add your solution here

Preview 0

WPF Increasing memory usage in time

4 solutions

Solution 3

Solution 4

Solution 1

Solution 2

Add your solution here

Preview 0

Existing Members

...or Join us