Critical Error versus Non-Critical Error Behavior
Posted: Thu Mar 16, 2017 3:20 pm
If this has been discussed elsewhere, please point me to that discussion.
Can anyone explain to me the mechanism that determines why some errors allow for "continue application" to be enabled and others disable this choice? My current best explanation is that some errors are critical and others are not. However, there must be a better way of understanding how this decision is made.
I have also noticed that for critical errors, it is possible that the error log is not updated before the application closes. My advice to end users if this happens is to capture the information in the Call Stacks menu with a camera before closing - because it may not be recorded in the log file. Is there a good reason why the log information is not written to the file for certain errors?
Can anyone explain to me the mechanism that determines why some errors allow for "continue application" to be enabled and others disable this choice? My current best explanation is that some errors are critical and others are not. However, there must be a better way of understanding how this decision is made.
I have also noticed that for critical errors, it is possible that the error log is not updated before the application closes. My advice to end users if this happens is to capture the information in the Call Stacks menu with a camera before closing - because it may not be recorded in the log file. Is there a good reason why the log information is not written to the file for certain errors?