Crash when shooting an enemy being resurrected by an Arch Vile

[ghost]

When shooting through an enemy (a shotgun zombie in this case I believe) in the process of being resurrected by an Arch Vile (shooting through the resurrecting enemy AT the Arch Vile), the game crashed. It occured a second time so I felt it was worth reporting. I was playing on Map 3(Aztec) of Plutonia if that makes any difference.

[bradharding]

Hmm. Thanks for this. I'll look into it. Are you able to add a comment here with the crash report from Windows event viewer?

[bradharding]

I've now had the chance to try to replicate this issue, but have been unable to do so. I've tried using v1.4.3, as well as the latest dev build, and in MAP03 of PLUTONIA.WAD, as well as other maps containing Arch-Viles. So a crash report would be extremely helpful! The Event Viewer is under Administrative Tools in the Control Panel. You'd select "Windows Logs" then "Application", and look for an application error like the following:

Faulting application name: doomretro.exe, version: 1.1.0.0, time stamp: 0x52e4b6f6
Faulting module name: doomretro.exe, version: 1.1.0.0, time stamp: 0x52e4b6f6
Exception code: 0xc0000005
Fault offset: 0x0002c83e
Faulting process id: 0x1388
Faulting application start time: 0x01cf1a66ef5d9df0
Faulting application path: C:\Users\Brad\Documents\GitHub\doomretro\msvc\Release\doomretro.exe
Faulting module path: C:\Users\Brad\Documents\GitHub\doomretro\msvc\Release\doomretro.exe
Report Id: 5592a7a0-865a-11e3-943c-d8a45fb783ec

[ghost]

Here you go. Hope this helps!

Faulting application name: doomretro.exe, version: 1.4.3.0, time stamp: 0x53717df0
Faulting module name: doomretro.exe, version: 1.4.3.0, time stamp: 0x53717df0
Exception code: 0xc0000005
Fault offset: 0x00018ca8
Faulting process id: 0x1ed0
Faulting application start time: 0x01cf93df35d5042b
Faulting application path: C:\Doom Retro\doomretro.exe
Faulting module path: C:\Doom Retro\doomretro.exe
Report Id: abdc1ab1-ffd2-11e3-9ea6-e0b9a5f30b85

[bradharding]

Thanks again moggimus! Was able to track down the cause and fix it quite quickly. Resolved in commit 80eb280.