DRD Team

I'm not sure what specifically is causing this, but I've had it a few times.

I don't know how many, of these steps are essential to get the crash, but here is the sequence of events that has managed to get it to happen 3 times for me.

I start a game which takes me to a skill selection map. I select a skill and then progress to the next map.

The next map is one that allows me to pick a specific level to play. I pick a level and go to it.

I start playing the level. For info, the level has lowered gravity and an echoey reverb applied to the whole map. The map also starts with a brief cutscene viewed through a camera object.

I start playing the level properly and get killed. I have the 3rd person deathcam enabled.

I hit [use] to restart the level.

I quit whilst the cutscene is still playing.

When I get to the Windows desktop, the crash dialogue is waiting for me.


The attached crash report is from my build of r184 which should be the same one as the one in the DRD folder.

It's the same sound bug that Randy and I have been discussing over at ZDoom without getting an idea where it comes from (meaning an actor gets killed without stopping all its sounds first.)

Given that I seem to manage it fairly reproducably with a release build, would me making a debug build be any help? Or have you already got all the information that a debug build can give you on this issue?

I haven't ever been able to reproduce this bug so if you can manage to get this bug in the debugger it'd be very helpful.

OK, following exactly the procedure that I outlined above, when I quit the game, the debugger showed me this. Is it of any use?



[edit] And doing it again got exactly the same result as far as I can see. [/edit]

Ok, Unfortunately it gives me nothing of value. Does this require soecific WADs? I see that you are autoloading a lot of stuff.


I had one more idea. Can you update and retry?

The original crash report was loading the stuff that I usually autoload.

The debug version was only loading my own Aspects IWAD and a second zip with models and some skyboxes in it. I can get the crash without the second zip but I loaded it because without it a lot of decorations are invisible due to the model for it not being there, so it's harder to wander around the levels.

I built r185 and ran it through the debugger, but the result looks very similar to me.



I know that you don't have the map, but would a savegame just before I quit be of any use?

I know that it will probably be useless, but it's getting late so I may as well upload this. It's a savegame. It was made with my debug build of r185.

The save was made after following the above procedure and saving just before trying to quit. If I restart a debug session and load the savegame, then quit again, I get the crash (repeatable 5 times). However, when I loaded into a release build, I didn't get it.

http://www.rowand.myzen.co.uk/savegame.zip

Too bad that the savegame is useless without the WADs it requires.


The thing is, the only way I can see to localize the problem is to run a scenario that crashes reliably with extensive debug output being added to the code. What's in the crash log is just symptoms, not the cause.

And, frustratingly, I have a scenario that crashes reliably but I have no way of getting it online. I suppose I could try and reduce things down to the point where only the levels and resources needed to get these maps up and running were in the WAD but that would take quite some time and there is no guarantee that it would still cause the problem once I'd done all that.

Is there any way you could add the extensive debug output to the code in such a way that I could give you meaningful feedback?

Sure. I'll do later today.

I don't think this provides any more information, but I'll post it anyway. This is with r186.



Any idea what settings I have changed to stop the disassembly tab appearing?

I don't know if you have tried to address this for r187 or not, but I still get the crash when following the procedure outlined above.

The first time I tried it with a debug build, GZdoom froze as I quit and I didn't get returned to the debugger properly. I saved the debug output to a text file (attached).

The second time I tried it, I was returned to the debugger. The following 2 screenshots were taken. The first as I was returned to the debugger and the second after pressing Break and killing GZdoom.





It looks like the same kind of information to me, so I'm going to guess that it is of little use.

This bug is really starting to annoy me.

r188

I'm sure that this won't come as a huge surprise, but just in case... My guess is that it wasn't expected to be related anyway, but the recent fix for the Strife flame thrower has not affected this problem.