Options
Memory profiling of windows service
Shlomi
Posts: 1 New member
Hi,
I took a first snapshot for the baseline than cause the service to do some work and took the second snapshot for comparison. from some reason the profiler cause the service to release most of its memory and thus I cant investigate the memory usage. same scenario without using the profile wont release the memory.
what I'm doing wrong?
Thanks for helping
I took a first snapshot for the baseline than cause the service to do some work and took the second snapshot for comparison. from some reason the profiler cause the service to release most of its memory and thus I cant investigate the memory usage. same scenario without using the profile wont release the memory.
what I'm doing wrong?
Thanks for helping
Tagged:
Answers
Hi and thanks for your post!
The profiler actually forces a garbage collection each time you take a snapshot and there isn't a way to disable this, I'm sorry to say.
It does this so that any objects which have no references will be released from memory (these are unlikely to be causing memory leaks since they can be released). The results can then focus only on the objects that are persisting in memory, which are likely to be causing any memory leaks.
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?