Crash: Possibly garbage disposal?

[Major Cooke]

Reposted with Graf's encouragement.
The original thread can be found RIGHT HERE.

---

Alright, I'm trying to figure out what's causing this issue to occur. What I want to do is find out what is causing it, and I've been looking through the stack trace to see what's wrong. It just spontaneously crashes when I'm playing (Yes, it's with aeons of death...) and I know this much, it's access violation.

Code: Select all

Unhandled exception at 0x003B1450 in gzdoom.exe: 0xC0000005: Access violation reading location 0xDDDDDDED.

Code: Select all

   291: 	template<class T> inline T *ReadBarrier(T *&obj)
   292: 	{
003B1440  push        ebp  
003B1441  mov         ebp,esp  
   293: 		if (obj == NULL || !(obj->ObjectFlags & OF_EuthanizeMe))
003B1443  mov         eax,dword ptr [obj]  
003B1446  cmp         dword ptr [eax],0  
003B1449  je          GC::ReadBarrier<DHUDMessage>+18h (03B1458h)  
003B144B  mov         ecx,dword ptr [obj]  
003B144E  mov         edx,dword ptr [ecx]  
003B1450  mov         eax,dword ptr [edx+10h]  <-------------------------------------RIGHT HERE
003B1453  and         eax,20h  
003B1456  jne         GC::ReadBarrier<DHUDMessage>+1Fh (03B145Fh)  
   294: 		{
   295: 			return obj;
003B1458  mov         ecx,dword ptr [obj]  
003B145B  mov         eax,dword ptr [ecx]  
003B145D  jmp         GC::ReadBarrier<DHUDMessage>+2Ah (03B146Ah)  
   296: 		}
   297: 		return obj = NULL;
003B145F  mov         edx,dword ptr [obj]  
003B1462  mov         dword ptr [edx],0  
003B1468  xor         eax,eax  
   298: 	}
003B146A  pop         ebp  
003B146B  ret  

Randy, If you need the files yourself, I'll upload them all to google docs and send them to you via PM, but only if you need them. To put it lightly, AEoD is getting yet another update scheduled to come out soon.

Here's the crash dump attached -- it's from running gzdoom via an earlier attempt but I have reason to believe it's the same one. Any ideas what might cause it?

[randi]

Does this only happen with an unreleased AEoD? If you record a demo and it crashes here, can you replay the demo and repeat the crash? That would be a big help, if so.

[Major Cooke]

Will attempt. And, I'm not sure. Does it require that I also send you the files (loaded .pk3s, the mod files) once finished, if I do replicate it?

[Major Cooke]

Also, sometimes the crash winds up being a "Couldn't allocate ####### bytes" error instead of an actual crash... Also does it matter if I use Zdoom or GZdoom?

[randi]

Does it require that I also send you the files (loaded .pk3s, the mod files) once finished, if I do replicate it?

Yes.

Also does it matter if I use Zdoom or GZdoom?

Maybe.

[Major Cooke]

Okay. I'm loading it up in google docs and sending it to you privately.

[Major Cooke]

The version which crashes in GZDoom is this one. Testing out the latest merged commits now to see if that makes a change...

Tested with this build of ZDoom (x64), no issues. GZDoom was recently updated, going to try it out and see if perhas the issue might have been fixed in it, but I won't hold my breath.

[Graf Zahl]

Any update on this? And don't forget that you still haven't linked the most important thing of all: The actual version of the mod that causes the crash!

[Major Cooke]

Either it was fixed on (G)Zdoom's side or in the mod itself. But it has not cropped up again so it's safe to say it's gone completely, I think.