We routinely test JustTrace against different workloads and profile targets and this behavior is unexpected. We need more data to resolve the issue. Is it possible to send us the the project (the binaries should be enough) so we can test against it? Another options is to send us a memory dump of the profiled process while it is working. We may also arrange an on-line meeting to debug the problem on your machine, if this is convenient for you.
In all cases, I suggest you to turn off the "Collect Call Stacks' option to speeds up the memory profiler while collecting enough information to solve large classes of memory leak. Also, running on a physical machine (and not inside a virtual one) also speeds up the profiling.
the Telerik team
Share what you think about JustTrace & JustMock with us, so we can become even better! You can use the built-in feedback tool inside JustTrace, our forums
, or our JustTrace