DRD Team

If I load up lights.wad and a wad that uses certain scripting effects gzdoom crashes HARD it spits out a blast of ear splitting static, bluescreens for a split second then restarts the computer.

Near as I can tell it happens whenever a script changes lighting colors. It happens in Daedalus during the decontamination sequence in the engine room airlock and in TNT1 when you hit the switch on the horde-of-cyberdemons-and-spidermasterminds-killing-machine.

If I don't use lights.wad it doesn't happen.

XP sp 2, gzdoom 1-0-04
I think all my lighting settings are default.

No problem here - in both maps.

Wierd, I just had it happen again in daedalus - this time in the engine core after the fire's been put out. And this time I didn't have lights.wad loaded. I just beat TNT1 with no problems though.

This sucks. I like gzdoom. All the niceness of zdoom + the prettiness.

Now that I think of it, I think I started out without lights.wad. And then ran for a while (on the same savegame) with it. Could that have affected it?

Any ideas on how to pin this down?

EDIT: Hmm I can't seem to reproduce that one. Nothing worse than a sporadic crash.

This sounds suspiciously like

http://forum.zdoom.org/potato.php?t=7893

and since I have full access to ZDoom as well I'll file this as a duplicate. But this is quite some elusive bug. So far neither Randy nor I have an idea what is happening. Randy has made quite a lot memory management related changes so maybe it gets fixed by those. Right now there's nothing I can do though without more detailed information (like a crash log for example.)

Unless the crash log gets puts somewhere other than the directory where gzdoom is I don't think there's much chance of getting a crash log. I wonder if I've got some crappy driver or something that's not playing nicely. I don't see how zdoom could crash the whole pc otherwise.