# SlicerApp-real.exe becomes non responsive when running my module

**URL:** <https://discourse.slicer.org/t/slicerapp-real-exe-becomes-non-responsive-when-running-my-module/30059>\
**Category:** Development\
**Created:** [June 15, 2023, 6:30pm UTC](https://discourse.slicer.org/t/slicerapp-real-exe-becomes-non-responsive-when-running-my-module/30059 "2023-06-15T18:30:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![drdH](https://avatars.discourse-cdn.com/v4/letter/d/ba9def/32.png) [@drdH](https://discourse.slicer.org/u/drdH)\
**Post date:** [June 15, 2023, 6:30pm UTC](https://discourse.slicer.org/t/slicerapp-real-exe-becomes-non-responsive-when-running-my-module/30059/1 "2023-06-15T18:30:14Z")

</div>

Team,

I am running custom slicer extension in debug mode. When the debug is started and my extension loaded the following happen:

1. I am able to run the Slicer UI for some time then it stops responding
2. The command prompt which shows my cout messages are all running despite the ui being un responsive.

Tools and OS used : Visual Studio 2022, Windows 10 OS, Slicer version 5.3.0

here are my questions:

1. Kindly wanted to know if there is a way to debug this or get a dump of message when the application goes non responsive?
2. Is there a windows tool or Slicer tool which gives such information?

Thanks

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [June 16, 2023, 2:01pm UTC](https://discourse.slicer.org/t/slicerapp-real-exe-becomes-non-responsive-when-running-my-module/30059/2 "2023-06-16T14:01:35Z")

</div>

Make sure you build the extension and Slicer with the same build options, on the same computer (e.g., you cannot run your extension with a Slicer release that you downloaded). If you experience hang then [you can debug it by starting Slicer from Visual Studio](https://slicer.readthedocs.io/en/latest/developer_guide/build_instructions/windows.html#debug-slicer). If you want to see what your application is doing anytime (for example when it is not responding) then you can use `Break all` action in the `Debug` menu in Visual Studio.