View Issue Details

IDProjectCategoryView StatusLast Update
0000461Gameplay + OpenGL[All Projects] Bugpublic2017-03-25 02:32
ReporterSleepyhead 
Assigned To 
PrioritynormalSeveritycrashReproducibilityrandom
Status closedResolutionunable to reproduce 
Summary0000461: QZDoom Crashes on Save w/ DukeShadows
DescriptionBasically, QZDoom 1.3.0.1 will randomly crash when loaded with DukeShadows 1.2 when saving. It doesn't happen exactly the same way every time but when saving each time I pick up a keycard, I tend to crash every 2-3 short maps, sometimes more sometimes less. I was able to determine that loading DukeShadows was the issue so I didn't think to post it here but I was encouraged to anyway.

Oh and I should also mention that "freak4.wad" is the levelset I was playing; I could play through it fine with QZDoom without DukeShadows and GZDoom 1.4 regardless of DukeShadows.

I've never done a bug report before so if I'm missing anything important, please tell me.
Additional InformationHardware Tested:
Operating System
    Windows 7 Home Premium 64-bit SP1
CPU
    Intel Core i5 4590 @ 3.30GHz
GPU
        4095MB NVIDIA GeForce GTX 970 (EVGA)
TagsNo tags attached.

Relationships

Activities

Sleepyhead

Sleepyhead

2017-03-21 17:29

reporter  

CrashReport.zip (20,616 bytes)
Sleepyhead

Sleepyhead

2017-03-21 23:22

reporter   ~0001081

Crashed again when saving; this time without DukeShadows; just stock QZDoom 1.3.0.1 (brightmaps and lights enabled) with a custom map. Now I'm well and truly confused. I'll add the crash report just in case it provides any insight onto the cause of this.

CrashReport2.zip (20,832 bytes)
dpJudas

dpJudas

2017-03-22 00:16

developer   ~0001082

Last edited: 2017-03-22 00:48

View 2 revisions

The callstack for this crash looks as follows:
>	qzdoom.exe!FSavegameManager::DoSave(int Selected, const char * savegamestring) Line 413	
C++
     qzdoom.exe!AF_FSavegameManager_DoSave(VMValue * param, TArray<VMValue,VMValue> & defaultparam, 
int numparam, VMReturn * ret, int numret) Line 443	C++
     qzdoom.exe!VMExec_Unchecked::Exec(VMFrameStack * stack, const VMOP * pc, VMReturn * ret, int numret) 
Line 682	C++
     qzdoom.exe!VMFrameStack::Call(VMFunction * func, VMValue * params, int numparams, VMReturn * results, 
int numresults, VMException * * trap) Line 466	C++
     qzdoom.exe!DMenu::CallTicker() Line 271	C++
     qzdoom.exe!M_Ticker() Line 731	C++
     qzdoom.exe!TryRunTics() Line 1947	C++
     qzdoom.exe!D_DoomLoop() Line 1029	C++
     qzdoom.exe!D_DoomMain() Line 2703	C++
     qzdoom.exe!DoMain(HINSTANCE__ * hInstance) Line 1035	C++
     qzdoom.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ * nothing, char * cmdline, int nCmdShow) 
Line 1345	C++

Since the crash is reported as "Access Violation - tried to read address FFFFFFFFFFFFFFFF", I'm guessing Selected is -1 and SaveGames is empty (TArray's Array member being null).

Edit: on second thought, it is more likely that savegamestring is somehow index -1 of a null pointer. Only thing I can think of that would use an unaligned pointer like that.

Rachael

Rachael

2017-03-23 20:48

administrator   ~0001093

Neither myself nor dpJudas have been able to reproduce this.

How much RAM does your system have and when was the last time you updated your NVidia drivers?

Beyond that, I really don't know what's happening here. Will have to get Graf to look at the savegame code for this.
Sleepyhead

Sleepyhead

2017-03-24 01:30

reporter   ~0001096

Last edited: 2017-03-24 03:53

View 2 revisions

I've got 8GB of ram on this machine. I'll try updating drivers and giving QZDoom a test run to see if I can get that to pop up again after the drivers are fully updated.

EDIT: Played through a few levels, so far so good. It might just have been my drivers being out of date. Feeling a little bit stupid but I'm just glad it works. Provided I'm not jumping the gun on assuming the problem is fixed, that is. I'll test it some more later on and if I can get through an episode of Doom 1 without crashing (which I couldn't before) then it's safe to say that this was just me being a bonehead.

Issue History

Date Modified Username Field Change
2017-03-21 17:29 Sleepyhead New Issue
2017-03-21 17:29 Sleepyhead File Added: CrashReport.zip
2017-03-21 23:22 Sleepyhead File Added: CrashReport2.zip
2017-03-21 23:22 Sleepyhead Note Added: 0001081
2017-03-22 00:16 dpJudas Note Added: 0001082
2017-03-22 00:48 dpJudas Note Edited: 0001082 View Revisions
2017-03-23 20:48 Rachael Note Added: 0001093
2017-03-24 01:30 Sleepyhead Note Added: 0001096
2017-03-24 03:53 Sleepyhead Note Edited: 0001096 View Revisions
2017-03-25 02:32 Rachael Status new => closed
2017-03-25 02:32 Rachael Resolution open => unable to reproduce