Activity overview
Latest activity by Jem.cox
Was this case study ever written or more information gathered? I appear to be witnessing a Heisenberg effect with my profiling as well. Actually, I would say this is more of a Hawthorne Effect than Heisenberg. I have been trying to track down a memory leak within a .NET Windows Service.
The VM size grows and grows and the service processes a flow of data from an MSMQ. When I turned ANTS profiler on for this service, however, the VM size became bounded at around 45MB, where it had grown over 100MB without the profiler. The number of objects also stabilizes.
I did a little digging and thought it may be because of the forced GC that the profiler does before capturing a snapshot. But even with my addition of a call to the GC to Collect, my memory still grows when I'm not profiling. I'm baffled but I certainly don't understand .NET garbage collection backwards and forwards yet. Just wanted some help understanding why the profiler might be behaving in this way.
I'm running the ANTS 2.7.0.109 free trial. On Windows XP SP2 on a Compaq laptop. / comments
Was this case study ever written or more information gathered? I appear to be witnessing a Heisenberg effect with my profiling as well. Actually, I would say this is more of a Hawthorne Effect th...