Regularly call MemoryUsed() and MaxMemoryUsed() to detect leaks before they cause a dump.
Is the crash happening in the or on a user's machine ? Do you have the source code for the version that crashed? dbgSaveDebugDump (Function) - PC SOFT Windev 18 dump
This command will output the exception code, faulting module, and stack trace. For a Windev 18 dump, you might see something like: you might see something like: