Closed NightFright2k19 closed 2 years ago
Very good bug report, thank you! Nevertheless, I cannot reproduce this issue with my 64-bit Linux build, even though precisely following your detailed instructions. Do you have anything in your autoload directories that might cause trouble?
I have some files in my autoload dirs, but they are purely cosmetic and shouldn't have any major impact on gameplay. I am attaching all files to make a 100% identical testing environment possible.
Included are:
autoload/doom.wad: d1spfx20.wad (sprite fixes) doom1wide.wad (widescreen gfx) greencross.wad (replacement for red crosses on medikits)
autoload/doom-all.wad: bloodcolor.deh (blood color fixes) bmap_fix.wad (fixes for some brightmaps) perk_sfx.wad (Per Kristian's Doom sounds)
I reproduce it, it crashes for me right on woofsav0 load. Backtrace:
00 0000001d`dcb1eb50 00007ff6`bf3a0505 woof!R_InterpolateTextureOffsets+0x91 [C:\develop\woof\src\p_spec.c @ 2679]
01 0000001d`dcb1eba0 00007ff6`bf3039dd woof!R_RenderPlayerView+0x225 [C:\develop\woof\src\r_main.c @ 821]
02 0000001d`dcb1f4d0 00007ff6`bf3075f3 woof!D_Display+0x24d [C:\develop\woof\src\d_main.c @ 285]
03 0000001d`dcb1f560 00007ff6`bf323728 woof!D_DoomMain+0x1433 [C:\develop\woof\src\d_main.c @ 2681]
04 0000001d`dcb1f630 00007ff6`bf3f8f62 woof!SDL_main+0x68 [C:\develop\woof\src\i_main.c @ 130]
05 0000001d`dcb1f660 00007ff6`bf3f6539 woof!main_getcmdline+0x132 [C:\projects\SDL\src\main\windows\SDL_windows_main.c @ 82]
06 0000001d`dcb1f6c0 00007ff6`bf3f63de woof!invoke_main+0x39 [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 79]
07 0000001d`dcb1f710 00007ff6`bf3f629e woof!__scrt_common_main_seh+0x12e [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 288]
08 0000001d`dcb1f780 00007ff6`bf3f65ce woof!__scrt_common_main+0xe [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl @ 331]
09 0000001d`dcb1f7b0 00007ffc`59d07034 woof!mainCRTStartup+0xe [D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_main.cpp @ 17]
0a 0000001d`dcb1f7e0 00007ffc`5b5e2651 KERNEL32!BaseThreadInitThunk+0x14
0b 0000001d`dcb1f810 00000000`00000000 ntdll!RtlUserThreadStart+0x21
R_InterpolateTextureOffsets
Oh, wow! What could go wrong here?
Here side_t *side = sides + s->affectee;
affectee
has garbage values, not sure.
I guess we need to convert affectee
to index and then to pointer etc.
https://github.com/fabiangreffrath/woof/blob/347e430c7101040fbca5bced6e5ec892f0e1cd66/src/p_saveg.c#L2693
@fabiangreffrath Can't you reproduce it? Every save load crashes for me here with uncapped.
the comment on dw brought me here
I've noticed that the ENDOOM screen is severly corrupted when exiting So I've checked the wad and the relative lump shows up in SLADE3 as graphic, not ansi text
removing the ENDOOM lump seems to prevent the game from crashing
I've noticed that the ENDOOM screen is severly corrupted when exiting So I've checked the wad and the relative lump shows up in SLADE3 as graphic, not ansi text
removing the ENDOOM lump seems to prevent the game from crashing
But I can't find ENDOOM lump in stickney.wad
I'm using the wad from the "StickneyE3V2.zip" linked in the wad's dw topic
Right, "StickneyE3V2.zip" has broken ENDOOM lump.
@fabiangreffrath Can't you reproduce it? Every save load crashes for me here with uncapped.
Yes, I have seen the crash meanwhile, though only very sporadically. Apparently, thinkers are recreated when a savegame is loaded. Strange that I have never encountered this when I tested my patch with a savegame of E2M4.
This patch fixes it for me:
This patch fixes it for me:
Perfect, please apply! 👍
NB: Please add a check to only add type == sc_side
scrollers!
For clearification: I had actually already removed the ENDOOM gfx from this modified wad (together with adding a UMAPINFO for hiding ep.4 and GAMEINFO for GZDoom), without knowing it could trigger anything, it just didn't seem right to have a normal image instead of a text lump. That's why I added the pwad in its entirety without just linking to it.
Anyway, the crash would happen without it as well.
Seems fixed with latest dev snapshot. Thanks, guys!
On E1M2 of "Stickney Installation", you get a crash to desktop with the following message after strafe-running across a slime pool with some platforms:
"I_Signalhandler: Exit on illegal storage access (Signal 11)"
Used Woof release: Latest Win64 workflow snapshot from "Master" branch (3046909730)
To reproduce:
Notes:
The attached zipfile contains:
stickney_test.zip