In the event of a crash, Directory Opus usually creates a log file (also known as a "dump file") with information that may be useful in diagnosing the problem.
(For problems which don't result in a crash -- e.g. freezes or abnormal CPU usage -- you can also manually snapshot Opus while it is running; see Manually generating process snapshots.)
Opus 13
Opus 13 has an automatic crash submitter built in - by default this is in the Help menu (Help / Submit Crash Logs). If you're using old or custom toolbars, the command is Help CRASHLOGS.
If Opus 13 won't start or won't run long enough for you to get to the crash submitter, please follow the steps below.
Opus 12 and earlier
To locate any automatically created crash logs:
- In Opus or Explorer, type %TEMP% into the location field and push return.
- Look for a sub-folder called DOpus.Minidumps. The actual path will look something like:
C:\Users\<username>\AppData\Local\Temp\DOpus.Minidumps. - If the folder exists it will contain one or more .dmp files, timestamped with the date and time of each crash.
The files are usually small but will compress to an even smaller size using 7z or Zip (from within Opus, right-click on it and choose Directory Opus Archives -> Add to Archive from the context menu).
Please email the compressed snapshot file to crashdumps@gpsoft.com.au.
The file may contain personal data so you should never attach it to a public forum post.
If the file is too large for your email service, even after compression, you could upload it to OneDrive, DropBox, or similar, and email the link to us.
When emailing crash logs, please include a link to the forum thread they relate to (or information on what happens, if there is no forum thread) so we know what we are looking for.
Please also note these two guides which may help narrow down problem causes and whether they are internal to Opus or the result of third-party components: