-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Runtime Issue]: Error 20 while trying to create crash dump #595
Comments
The first dialog with the path to the crash dump will be shown after the crash dump was successfully written by Windows The second dialog only appears in case that MiniDumpWriteDump() function returns with false. I can't reproduce getting that dialog after clicking OK on the first one. |
It looks like I do have a crash dump there. I guess that the second dialog box needs to be reworded in order to make it clear that at least one crash dump has been written successfully. |
That's the thing, you should only get one of the dialogs not both. Unless it just crashed again and couldn't write the dump the 2nd time. But I can't reproduce that scenario. The game just closes for me, after clicking OK on the first dialog. Btw. did you run a GitHub artifact or a self build version? If GitHub artifact, can you please share the crash dump file? |
I just updated the steps to reproduce for #594. If you follow those new steps to reproduce, do you get the second dialog box?
I built the game myself. |
Unfortunately I still can't reproduce this. |
Build Version
v1.6 770e9e8
Operating System Environment
CPU Environment
Game Modes Affected
Game Environment
I’m using game data from the US Windows Dual-Jewel version of Descent 3 v1.4.
Description
Sometimes, Descent 3 will encounter an error and try to save a crash dump:
Unfortunately, when you click on the OK button, it gives you this error:
Regression Status
I don't know
Steps to Reproduce
Do something that would cause Descent 3 to crash and produce a crash dump. At the moment, you can do so by trying to reproduce this issue.
Once the “Unexpected Error” window appears, click “OK”.
The text was updated successfully, but these errors were encountered: