Problem profiling Desktop Application
Indy7
Posts: 2
Hi,
We just purchased ANTS Profiler 3.2 to profile our .NET 3.5 based Desktop application. Our VS2008 application solution is fairly large, consisting of 37 projects. (My development PC is configured with Pentium4 2.99GHz, 2GB RAM).
Every time I click the 'Take Snapshot' button (regardless of whether ANTS Profiler was started from within VS2008 or as a stand-alone app. with VS2008 closed) after ANTS Profiler successfully started the application, ANTS Profiler can not complete the task and instead it closed the application to be profiled and comes up with the error message 'The profiled application has exited whilst sending data, profiling will now stop. Please try again'.
I'm pretty much clueless at this point as to the cause of this problem that prevent us from profiling our Windows Forms (not WPF) desktop-application.
I would appreciate it if somebody from ANTS Profiler support group can response to this problem.
Regards,
Indy
We just purchased ANTS Profiler 3.2 to profile our .NET 3.5 based Desktop application. Our VS2008 application solution is fairly large, consisting of 37 projects. (My development PC is configured with Pentium4 2.99GHz, 2GB RAM).
Every time I click the 'Take Snapshot' button (regardless of whether ANTS Profiler was started from within VS2008 or as a stand-alone app. with VS2008 closed) after ANTS Profiler successfully started the application, ANTS Profiler can not complete the task and instead it closed the application to be profiled and comes up with the error message 'The profiled application has exited whilst sending data, profiling will now stop. Please try again'.
I'm pretty much clueless at this point as to the cause of this problem that prevent us from profiling our Windows Forms (not WPF) desktop-application.
I would appreciate it if somebody from ANTS Profiler support group can response to this problem.
Regards,
Indy
Comments
I think this may be an unavoidable situation caused by .NET 2.0's critical finalization procedure. If an application domain is unloaded or a problem happens that causes .NET to run finalization, the process that .NET uses to clean up all resources in use by your application takes down the communication between ANTS Profiler and the application itself, because this communication is done through a named pipe. Please see here for more information.