Activity overview
Latest activity by tony
I got the logs and they imply there is no memory problem...
PhysMemInUse: 980 (Mb), VirtMemInUse: 150 (Mb), PhysMemAvail: 41 (Mb) - EndGarbageCollection (start)
this is the last memory log before the error. After the error the profiler has no problem using more memory up in creating the final snapshot.
It seems the profiler is making the Drawing routine think it has no memory! / comments
I got the logs and they imply there is no memory problem...
PhysMemInUse: 980 (Mb), VirtMemInUse: 150 (Mb), PhysMemAvail: 41 (Mb) - EndGarbageCollection (start)
this is the last memory log before t...
Memory profiler causes an OutOfMemoryException
I've just used the memory profiler for the first time since upgrading to .Net 2.0.
I have an application that works fine on its own, in debug, and with the performance profiler.
I try to run the me...