This question is locked. New answers and comments are not allowed.
I have just installed JustTrace onto a server and I am able to start a new profiling session and attach to a w3wp process in which my C# MVC3 website is running.
I see the memory usage but when I then try to take a snapshot, I just see the Getting snapshot dialog box, but it never seems to finish. I have waited for around 30minutes and the memory of the process at the time is around 1GB-2GB.
I am using Trail Version Q2 2013 Internal Build 2013.2.702.0.
Is there anything I have not configured ? Could it be the debugging tools I am using which are configured in the Options menu?
I have no idea how to sort this out, any help would be greatly appreciated.
Cheers
I see the memory usage but when I then try to take a snapshot, I just see the Getting snapshot dialog box, but it never seems to finish. I have waited for around 30minutes and the memory of the process at the time is around 1GB-2GB.
I am using Trail Version Q2 2013 Internal Build 2013.2.702.0.
Is there anything I have not configured ? Could it be the debugging tools I am using which are configured in the Options menu?
I have no idea how to sort this out, any help would be greatly appreciated.
Cheers
1 Answer, 1 is accepted
0
Hello Rupert,
Unfortunately sometimes getting a memory snapshot when you attach to a running process is quite slow. It can indeed take hours in some cases. This depends more on the object graph's complexity than on the heap size itself. Having a large number of alive objects in memory may be the reason that it's taking so long in your case.
I would suggest that you start your profiling session with a fresh worker process through JustTrace's IIS locator. See http://www.telerik.com/help/justtrace/profilee-types-asp.net-(iis).html for more information. This way getting a snapshot should be a lot faster. For maximum performance I recommend that you do not enable the Collect allocation call stacks and the Accurate object age options.
If you have any questions or you need further assistance, please do not hesitate to contact us again.
Best regards,
Martin
Telerik
Unfortunately sometimes getting a memory snapshot when you attach to a running process is quite slow. It can indeed take hours in some cases. This depends more on the object graph's complexity than on the heap size itself. Having a large number of alive objects in memory may be the reason that it's taking so long in your case.
I would suggest that you start your profiling session with a fresh worker process through JustTrace's IIS locator. See http://www.telerik.com/help/justtrace/profilee-types-asp.net-(iis).html for more information. This way getting a snapshot should be a lot faster. For maximum performance I recommend that you do not enable the Collect allocation call stacks and the Accurate object age options.
If you have any questions or you need further assistance, please do not hesitate to contact us again.
Best regards,
Martin
Telerik