DRD Team

Probably not much use to you because it's my build, but here you go. A few times GZdoom has crashed at startup, dumping me back to the desktop with a crash log. I can then restart GZdoom in exactly the same way and it works.

In the remote hope that it helps somehow, here's a crashlog.

Oh, the file being loaded (flassssssssssssh.zip or whatever it was) is just the test file from my other bug report about dynamic lights. It has happened without that file loaded.

I have tried to get a debug build to fall over, but it hasn't done so.

I just got it once, too. Unfortunately the crash log didn't help me much...

Not much to add other than to give you an idea of the frequency of this problem. Since reporting it, it has happened to me 4 times. I've played quite a bit of GZdoom in that time so it isn't very frequent but it's obviously still there.

I don't know if it can happen during a game. It hasn't happened to me but most of my sessions have been short ones for testing stuff rather than extended playing.

Just for the record, although it hadn't happened for a while, I got 3 of these in a row this morning with r165. although I have r168 compiled I wasn't actually using it at the time because of the black blood particle bug imported from Zdoom.

I assume this is still the same thing. This is with r180. If there is any other info you think might be useful, like a copy of the WAD being loaded, I can send it to you. However, trying to restart GZdoom in exactly the same set of circumstances did not give a crash.

Unfortunately your crash report doesn't match the map file posted in the SVN builds folder. So I can't investigate. From the rough address it looks like it's happening in the JPEG decoding code but no guarantees without a proper map file to look it up.

Dammit, That's strange because I'm pretty sure the build of r180 in the builds folder is my own. Perhaps I rebuilt it or something, or maybe it isn't my one.

[edit]Comparing the two, they are different. I remember SoulPriestess talking about re-uploading r180 so that the file got sorted to the top of the list after the server move. So perhaps she made a new build. Or maybe I'm just remember things wrong.[/edit]

However, looking at the time stamp in this map file, I think this is the one from the build I was using when I got the crash.

http://www.rowand.myzen.co.uk/180mapfile.zip

I'm not sure how to use a mapfile myself. I noticed that in the crash report I posted, there is the word "BOOM" beside this number 005f41fa. I searched for that in the mapfile but couldn't find it. Is that any where near what you are meant to do?

The important address is the last call before the BOOM - which in this case points to memcpy, called from InitializeActorInfo.

And that function passed a value that was too large to memcpy.