Hi Dave,
Can you tell how do you profile your memory usage? Do you get a statistic
of your memory usage or do you use a profiler to get the call graph of the
memory allocation?
The normal diagnostic steps for memory issues are:
1. Use Task Manager and the System Monitor to confirm the memory leaks.
2. Use windbg in conjunction with the SOS extension to pinpoint where
managed memory is allocated in an application.
3. Use Allocation Profiler to show how managed memory has been allocated,
and also can be used to find object roots.
For details see the article below:
"Debugging Memory Problems"
http://msdn2.microsoft.com/en-us/library/ms954591.aspx
Specific, you may read "Diagnosing Memory Leaks with the Allocation
Profiler" section to understand how to get the call graph of the
allocations for these GPStream objects.
Thanks
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.