Description
Background
I was messing around with a custom SLIGE wad for Ultimate Doom. When I put it in Chocolate Doom for E4M1 and it segfaults, which seemed kind of odd. I tried other levels on the wad and they all worked fine. E4M1 also worked normally (the Ultimate Doom level). I tested it on 2 versions of Chocolate Doom to make sure this wasn't an already fixed bug.
Version of Chocolate Doom:
3.0.0 (first try)
Latest from Github (second try, same segfault)
Operating System and version:
Debian 10 Buster, fully updated and stable.
Game: (Doom/Heretic/Hexen/Strife/other)
Doom (Ultimate) w/ Custom SLIGE wad
Any loaded WADs and mods (please include full command line):
chocolate-doom -file ultrawad.wad
&
chocolate-doom -merge ultrawad.wad
were both tried on both versions
Bug description
Observed behavior: Segmentation Fault one second after E4M1 on custom wad loads (consistently)
Expected behavior: I expected a different error (like a DOOM original engine bug), or for it to load the level normally.