Enable dump on Exception
when we enable the Dump on exception for Full dump in configuration wizard the registry setting “Terminate Process on exception” changed from 0 to 1. Is this a normal behavior?
We want to know after the collection of dump by workplace whether workplace automatically closed or not?
Voted best answer
A number of registry keys controling the vectored exception handler are modified by the Dump on exception setting in the configuration wizard.
Since a process that have run into an exception may be in a chaotic state and unable to figure out that it is time to quit it was decided to force it to do so.
The workplace will need to be restarted manually after an exception (regardless on the dump setting) while other Afw-services (that are also covered by the dump setting) will be restarted automatically.
As stated in first answer; disable dumping as soon as possible and do not have it active in more than a few clients or servers at a time.
Dumping will deactivate any internal crash protection/handling and force process to dump & quit even if the crash protection/handling could have saved it from crashing. The setting is global per computer and will affect all 800xA processens, not just the workplace. Keep an eye on the OperateITTemp/Dump folder as is may grow out of bounds and eventually fill the disk if left active/unattended.
Dump on Exception is used in exceptional cases and not a regular setting that should be enabled in running plants.
Following happens by enabling this setting..
- Registry setting “Terminate Process on exception” changes from 0 to 1
- Workplace will close automatically as soon as there is any exception.
- Crash dump will be collected in "Dump" folder.
Even if this setting is enabled for some reason, it should immediately be reverted once the dump is collected to avoid frequent workplace crashes and filling up of hard disc with crash dumps.