0

I set registry values to make a crash dump (like here).

It works great for small applications (few megabytes).

When my application is huge, almost 2GB in ram memory and when it crashes, the dump file is created in specified directory. During dump creation application is in 'frozen state'. When user click on this frozen application, system stops creating dump, and remove active dump file from dump directory.

Have anyone idea how can I prevent this situation?

Community
  • 1
  • 1
LukaszTaraszka
  • 801
  • 1
  • 10
  • 26
  • It's not enough to click on the non-responding application. The user must also select the button to kill the application. – Thomas Weller Mar 17 '17 at 15:10

1 Answers1

1

There are two Registry entries that influence the behavior: HungAppTimeout (MS Technet) and WaitToKillAppTimeout (MS Technet).

Another approach is the per-application setting DisableProcessWindowsGhosting (MSDN). This requires some modification in your code: calls that method to prevent window dimming. This will affect all users.

If you don't want to change it in your code, you can apply the same setting with the "NoGhost" option of Application Compatibility Toolkit (MS Technet). This can be done on a per PC basis.

Thomas Weller
  • 55,411
  • 20
  • 125
  • 222