No results for console app

Brian Donahue

Hi Brett,

Thanks for posting. The problem could either be that the behavoiur of the 'Stop' button has changed or because of the multithreading nature of the application.

If you click stop in the new version, you may not get results like you did in the previous version. This is because we do not want to close the application on users who are doing memory profiling, because all of the objects would be freed and the memory profiling would be invalidated.

If you have a multithreading console app and try to stop it by closing the console window, you may not get results because ANTS Profiler didn't get notified that the application had stopped. Try closing the application by letting it run till the end, or use the snapshot function before closing the console window.

Brian Donahue

ANTS Profiler 2.5 should now correctly detect that an application has exited, regardless. ANTS Profiler will not hang around forever waiting for all of the threads to terminate.