New CLR Profiler for .NET Framework 4
We just found a memory leak (again) in our latest code base that we’re going to release to production next month, seems that we’re having this issue for every release :p i think it’s unavoidable considering the amount of changes that we’re making on the app for each release ;)
Now, when I tried to do the regular steps to investigate the root cause, the CLR Profiler was not responding when I clicked the Show Heap now button and eventually display the pop-up below.
Then realised that since we have just upgraded the application to use .Net 4.0, so there’s a chance that there’s a new CLR Profiler on the block for .Net 4.0, and turned out there is actually a new one available in MSDN. And it’s not surprising, considering that .Net 4.0 comes with a new CLR as well (click on the image below to go to the msdn website for more info)
After downloaded the new CLR Profiler 4, it looks like below, notice the new Attach Process and Detach Process buttons, those will be very useful as we always need to start the application in the previous version, sweet! :)
Now, it’s time to duck into the the heap :)
Memory leaks?? Surely not ;)
Did i just say memory leaks? of course it’s not, it’s just some objects comfortably overstayed in the heap, that’s all, nothing to worry about :p
How are you m8? hope things are going great on your side ;)