Skip to content
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

Open
13 of 20 tasks
Jayman2000 opened this issue Sep 19, 2024 · 5 comments
Open
13 of 20 tasks

[Runtime Issue]: Error 20 while trying to create crash dump #595

Jayman2000 opened this issue Sep 19, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@Jayman2000
Copy link
Contributor

Build Version

v1.6 770e9e8

Operating System Environment

  • Microsoft Windows (32-bit)
  • Microsoft Windows (64-bit)
  • Mac OS X
  • Linux (specify distribution and version below)

CPU Environment

  • x86 (32-bit Intel/AMD)
  • x86_64 (64-bit Intel/AMD)
  • ARM (32-bit)
  • ARM64 (64-bit; sometimes called AArch64)
  • Other (RISC V, PPC...)

Game Modes Affected

  • Single player
  • Anarchy
  • Hyper-Anarchy
  • Robo-Anarchy
  • Team Anarchy
  • Capture the Flag
  • Bounty
  • Entropy
  • Hoard
  • Monsterball
  • Cooperative

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:

Unexpected error

Crash dump file written to:
C:\Users\ANONY~1.MOU\AppData\Local\Temp\d3-crash.tmp
You can attach it to a bug report.

OK

Unfortunately, when you click on the OK button, it gives you this error:

Unexpected error

Could not create crash dump file, error code: 20

OK

Regression Status

I don't know

Steps to Reproduce

  1. 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.

  2. Once the “Unexpected Error” window appears, click “OK”.

@pzychotic
Copy link
Contributor

The first dialog with the path to the crash dump will be shown after the crash dump was successfully written by Windows MiniDumpWriteDump() function.
Do you have a crash dump file at that location?

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.

@Jayman2000
Copy link
Contributor Author

The first dialog with the path to the crash dump will be shown after the crash dump was successfully written by Windows MiniDumpWriteDump() function.
Do you have a crash dump file at that location?

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.

@pzychotic
Copy link
Contributor

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?

@Jayman2000
Copy link
Contributor Author

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.

I just updated the steps to reproduce for #594. If you follow those new steps to reproduce, do you get the second dialog box?

Btw. did you run a GitHub artifact or a self build version? If GitHub artifact, can you please share the crash dump file?

I built the game myself.

@pzychotic
Copy link
Contributor

Unfortunately I still can't reproduce this.
This seems more like a niche annoyance in rare occasions right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants