I've reviewed the code in each method to release resources and call Dispose if needed. I have also checked some counters with perfmon and clr_profiler, but no clue of what is causing this behavior. Please help me
public static long GetTotalMemory (
bool forceFullCollection
)
Interesting that it does not happen on workstation but does on server.
This is not a fix for a leak, but what happens if you set your application on workstation to use server style garbage collection You might also try non-concurrent collection.
<configuration>
<runtime>
<gcServer enabled="true"/>
<gcConcurrent enabled="false"/>
</runtime>
</configuration>
MarianoMazzieri wrote:
It made no difference for win2k worksattion, it is stable anyway... What i want is that the Win2003 to behave the same way...
Thanks for posting those good advises... Sadly i haven't found the cause of the leak. Even more, i've checked counters for every generation and i've found that total bytes in gen 2 are increasing constantly... but then again, when i run the same test on Windows 2000, it works perfectly fine like clock: no leak.
Is it anything about Windows Server 2003 and framework 1.1 This is making me crazy...