There's no CF 2.0 tool that will directly pinpoint where the allocation was
made but not released (though RPM 3.5 also has a profiler tool that will
show this, so installing Studio 2008 beta for this tool might be useful).
It sounds like you are creating a new task list form every time but still
holding some reference to the old one (like in an event handler) so they're
stacking up (no pun intended) in the Heap.

Signature
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
> Users of the application I have developed report an occasional
> OutOfMemoryException. This prompted me to do some research on memory
[quoted text clipped - 17 lines]
> Thanks for any suggestions!
> Daan
Daan - 16 Aug 2007 15:55 GMT
> There's no CF 2.0 tool that will directly pinpoint where the allocation was
> made but not released (though RPM 3.5 also has a profiler tool that will
[quoted text clipped - 32 lines]
>
> - Tekst uit oorspronkelijk bericht weergeven -
Every time the 'details' view is displayed, 25 new custom controls are
created to display the details of the task. When the 'list' view is
displayed, the panel and any list that contains the 25 custom controls
are cleared. I have tried adding code that removes the event handler
from the items on the panel before clearing the panel.Controls, but
this does not solve the problem. Is there any other way (other then
event handlers) that a reference can still exist to the objects, even
though they are cleared from the panel?
Peter Morris - 16 Aug 2007 21:36 GMT
Are you also calling Dispose on those controls, or on a single parent of
those controls? If not then your app might be holding onto handles.
I have also had problems with OutOfMemoryException.
http://mrpmorris.blogspot.com/2006/12/cf-outofmemory-or-maybe-not.html
Pete