Understand crashed — how do I report it?¶
Getting the crash details to SciTools is the fastest path to a fix. What happens automatically depends on your platform.
Windows — automatic error reporting¶
On Windows, an unhandled crash triggers the built-in reporter, which shows a “SciTools Support” dialog with Send and Send With Dump File buttons. Whether it prompts is controlled by Help → Privacy (the Privacy & Error Reporting page): report automatically, ask each time, or never.
Behind the scenes it writes:
- A crash log appended to
%APPDATA%\SciTools\<app>.log— includes OS, build number, message, workfile, exception code, loaded modules, and the stack. - A minidump under
%TEMP%\SciTools\named<app>-<build>-<YYYYMMDD>-<HHMMSS>-<pid>-<tid>.dmp.
Choosing Send With Dump File uploads both, which gives support the most to work with.
macOS / Linux — send the details manually¶
No automatic crash upload on macOS or Linux
The automatic reporter is Windows-only. On macOS and Linux, Understand does not capture or upload a crash automatically. Email the details to [email protected] — include your Understand version/build, your OS version, and what you were doing when it crashed. If your OS produced a core/crash file, attach it.
Always helpful: your build number and analysis log¶
- Build number: Help → About Understand.
- Analysis log: Help → Send Analysis Log… opens a pre-addressed email to [email protected] (this is the analysis log, not the crash log — send it when the problem is bad/incomplete analysis rather than a hard crash).
Related¶
- “Failed to load the model file” — an AI-model error, not a crash.
- Understand won’t start