Improved application error handling and crash recovery

When a crash is detected, Sonar now attempts to close any files that have been opened for recording, before terminating the application. This allows the wave files to be properly saved and terminated allowing you to reimport the files imported from the audio folder manually, in the event of a crash.

Sonar has integrated error reporting and an Exception Severity setting (see Plug-in exception handling / crash reporting). While exception severity values of 3 and higher can be useful to preemptively catch certain crashes, it was found that this could occasionally aggressively report crashes that are actually internally handled by the OS or certain plugins. As a result, Sonar defaults to a value of 1 (Unhandled errors).

In this release, Sonar's error management has been greatly improved to resolve some stability issues and detect several more classes of errors by default, without the need to boost the ExceptionHandlingSeverity. The new mechanism should resolve issues where crashes could silently occur with Windows terminating the app without an error report or giving you a chance to save your work.

 

Errors are now detected in the UI, as well as the engine and plugins in more cases. In all cases a crash dialog will be shown and a minidump and error log will be saved to the crash reports folder at %appdata%\Cakewalk\Sonar\MiniDumps. The crash dialog and error log format has also been improved to show more information for the new error types.

 

See:

New features