12.3 · Troubleshooting

Crash Reports and Logs

Tex catches unhandled exceptions with a global handler and presents them through CrashReportDialog. There is currently no on-disk log file — routine logging goes to the debugger only, and crash dumps are the primary diagnostic artefact.

Crash report dialog

Shown automatically whenever an unhandled exception reaches the App-level handler.

Field	Contents
Exception	Type, message, and full stack trace
App version	Tex version string
System info	OS version, architecture, .NET runtime

Buttons

Button	Action
Send Bug Report	Opens your default email client with the payload prefilled
Copy Details	Copies the exception + system info to the clipboard
Open Report Folder	Opens `%APPDATA%\Tex\crashes\` in Explorer
Close	Dismisses the dialog and terminates the app

Crash file storage

Crash dumps are written to %APPDATA%\Tex\crashes\ as timestamped files. Keep these when raising a support ticket — the stack trace alone is enough to triage most issues.

Routine logs

Routine logging uses the Microsoft.Extensions.Logging.Debug provider at LogLevel.Information. Output goes to the Visual Studio Debug console only — there is no persistent log file at present.

What gets logged

App startup and shutdown.
Settings load / save (including corrupt-file recovery).
Hotkey registration results.
Service initialisation (OCR, auto-update, licensing).
Warnings for hotkey conflicts, license validation timeouts, and fallbacks.

Tip

Tip — Run Tex.Wpf.exe from a command prompt to see any stdout / stderr output. Most logging still goes to the debugger rather than the console, but unhandled startup errors that occur before the crash handler is wired up will appear here.

Reporting a bug

Reproduce the crash (or capture Copy Details from the dialog).
Click Send Bug Report, or attach the newest file in %APPDATA%\Tex\crashes\ to an email.
Include: what you were doing, the Tex version, and whether the issue is reproducible.

See 12.1 for non-crash common issues.
See 12.2 for hotkey-specific diagnostics.