Thank you for reporting this.
You are correct that the JustTrace profiler
remains attached to a running process even after Detach Profilee
has been hit. You are also correct that stopping or restarting JustTrace is not changing the above either. It is unfortunate to say but for now, the only way to remove our profiler from the profiled process is to restart that process.
This is due to the fact, the Detach Profilee
button is only disabling the JustTrace profiler inside the profiled process and saving the current session afterwards. This means the Detach Profilee
button is almost the same as Kill Profilee
(when profiling a .NET Executable, for example), but instead of killing the profiled process it leaves the JustTrace profiler disabled in it. So, to actually detach our profiler from a once profiled .NET running process, you will need to restart that current process, the same as other profilees being automatically killed by JustTrace (Kill Profilee
) when the profiling session has ended.
I hope this helps.
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