WeakReferences are not freed in embedded OS

Posted by Carsten König on Stack Overflow See other posts from Stack Overflow or by Carsten König
Published on 2012-04-16T11:25:02Z Indexed on 2012/04/16 11:29 UTC
Read the original article Hit count: 243

Filed under:
|
|

I've got a strange behavior here: I get a massive memory leak in production running a WPF application that runs on a DLOG-Terminal (Windows Embedded Standard SP1) that behaves perfectly fine if I run it localy on a normal desktop (Win7 prof.)

After many unsucessful attempts to find any problem I put one of those directly beside my monitor, installed the ANTs MemoryProfiler and did one hour test run simulating user operations on both the terminal and my development PC.

Result is, that due to some strange reasons the embedded system piles up a huge amount of WeakReference and EffectiveValueEntry[] Objects.

Here are are some pictures:

Development (PC): enter image description here

enter image description here

And the terminal: enter image description here

Just look at the class list... enter image description here

Has anyone seen something like this before and are there known solutions to this? Where can I get help?

(PS the terminals where installed with images prepared for .net4)

© Stack Overflow or respective owner

Related posts about c#

Related posts about memory-leaks