Why Does Dyalog Crash or Close Unexpectedly on Windows?

Unexpected crashes or silent exits usually indicate that Windows encountered an unhandled exception. Collecting a crash dump allows Dyalog Support to diagnose the underlying cause.

Why This Happens

In most cases, Windows terminates the process due to an unhandled exception, a system-level fault, a missing dependency, a stack overflow, or a driver/runtime issue.

Enable Crash Dump Generation (Windows)

Create the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

Inside LocalDumps, create a new DWORD value:

• Name: DumpType
• Value: 2

Where Dump Files Are Stored

After a crash, Windows typically writes dump files to:

C:\Users\<YourUserName>\AppData\Local\CrashDumps

Providing Information to Dyalog Support

If a .dmp file is created:

• Compress the file
• Contact Dyalog Support for upload instructions
• Include the Build ID of the Dyalog executable.

Disk Space Consideration

Crash dumps can be large. Periodically review the CrashDumps directory to avoid unnecessary disk usage.

Summary

Unexpected crashes are typically caused by exceptions.  A crash dump may provide clues to diagnose the issue.  Please try to reproduce the crash.   Sending Support a way to reproduce it is the best way for the developers to fix the issue.