latest gzdoom freezes after a few minutes

Forum rules
Please be as descriptive as possible in your posts (list your hardware and operating system, the version of the source port you are using, any mods you are running and how they're being loaded, etc.)
This will help others to give you a solution!

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: latest gzdoom freezes after a few minutes

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Sun Aug 22, 2021 7:39 am

Graf Zahl wrote:Prepare to buy some new hardware soon. This sounds like some component in your system is coming close to the end of its lifespan.
Fixed by replacing the sound card. Shouldn't have questioned the above response.

@mods pls close the thread

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Sun Oct 25, 2020 6:02 am

Seems fixed in latest GZdoom 4.4.2.

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Mon Mar 04, 2019 11:53 am

Tried Attaching debugger to Process.
Checked twice -- freeze occured when trying to use some kind of EFX (according to code), which is a common thing in PSXDOOM TC maps (Reverb).
Still not sure what particular Effect might be causing this -- when I played, Reverb seemed to work fine. Maybe I'll investigate this later.

Anyway, disabling SND_EFX seems to have resolved the issue.

Doublechecked -- loaded map61 Attack and ran through the entire level with Noclip, so that Reverb Environments could change quickly.
As soon as I've enabled EFX, restarted sound and walked through the map -- gzdoom froze after a while.

I'll try testing further (wanted to play psxdoom anyway), and get back with results.

Thanks for your assistance so far.

Re: latest gzdoom freezes after a few minutes

by _mental_ » Mon Mar 04, 2019 4:57 am

I would look for two (or maybe more) threads that wait on the same critical section. This is relatively easy to do using Parallel Stacks window in Visual Studio.
BTW, you can copy/paste a callstack from the corresponding window. There is no need to create screenshots.

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Sun Mar 03, 2019 12:03 pm

Built debug openal32 successfully using cmake-3.14.0-rc3-win64-x64 GUI
vs2019 project https://drive.google.com/open?id=1iVHjv ... iUxvSuv6Zt
Problem reproduced.
Im afraid I don't have enough experience to see what's going on. Is that where these "hints" are supposed to be?
[imgur]https://imgur.com/a/ExS8YSK[/imgur]
Crash dump: https://drive.google.com/open?id=1Bo6DW ... tTY9DtVEfW

Re: latest gzdoom freezes after a few minutes

by _mental_ » Sun Mar 03, 2019 10:40 am

Well, it’s possible to build Debug version of the latest OpenAL release and replace .dll in GZDoom folder.
This won’t resolve the issue but will probably give some hints about the real cause of the crash.

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Sun Mar 03, 2019 10:31 am

This time GZdoom Crashdump was created: https://drive.google.com/open?id=1R5_eY ... uQ3QRB9nLe

I don't have the debug symbols for the openal32.dll
Spoiler:
Is it possible to resolve this somehow?
Thanks for all your feedback so far.

Re: latest gzdoom freezes after a few minutes

by Guest » Sat Mar 02, 2019 4:49 pm

[img]https://i.postimg.cc/cCJPj7s0/openal.png[/img]
With -nosound, there was no such crash -- no mention of openal32, and I think it'd crashed anyway with same steps I followed -- change virtual resolution to very high values (so probablythere's no need to investigate this case yet).

If the issue is really in OpenAl,
Do I need to build my own opernal32.dll? Is it possible to get some kind of OpenAL debug/verbose info (about this specific AlSourcePlay 0x79 issue)?

Re: latest gzdoom freezes after a few minutes

by _mental_ » Sat Mar 02, 2019 12:37 am

lafoxxx wrote:what tool do you use to analyze memory dumps?
Tried windbg from Windows 10 SDK -- it didn't find any exceptions (or maybe I simply don't know how to use it).
I’m using Visual Studio 2017, 2015 should work too. Actually, WinDBG is enough to check dumps. You need to use Microsoft symbol server in WinDBG to get meaningful information in callstacks.

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Fri Mar 01, 2019 3:13 pm

Freeze now appears randomly, or doesn't appear at all

First, it crashed after changing some options, including switching OpenAL device from Default to "OpenAL Soft on SB X-Fi (B)" and performing writeini shortly thereafter (sorry -- no dump)

When Sound Device was Default, don't remember encountering any crashes. But that's the only device -- "OpenAL Soft on SB X-Fi (B)", which should be used when Default is selected.
Maybe it's just a coincidence (I was impatient and changed openAl device to "OpenAL Soft on SB X-Fi (B)"), but "after" does not mean "due to" here, IMO.

Most recently -- used ini based on PSXDOOM.INI with some changes (writeini) from previous crash

I was playing with Resolution Scale

Caught freeze again with -nosound and just psxtc.pk3 psxtcmus.pk3 (no psxdoom customizer)

Dump is now 5.62 gb https://drive.google.com/open?id=1KdtYI ... _avu9Kuwta
gzdoom ini https://drive.google.com/open?id=16bCIs ... iHDH5DXIY6

not sure if the crash reason is same as in my initial message (video memory overflow -- just a guess)


btw, @_mental_, what tool do you use to analyze memory dumps?
Tried windbg from Windows 10 SDK -- it didn't find any exceptions (or maybe I simply don't know how to use it).

I'll try with clean gzdoom cfg created from scratch, no change in options at all.

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Fri Mar 01, 2019 10:03 am

Actually the sound card is the only old component (besides few hard drives). Thanks for the guess.
Makes sense because it's OpenAL device.

Still haven't tried with No sound.


Tried the following instead:
Deleted all Configs
Played clean doom2.wad fine
Played doom2+psxtc.pk3 fine
Played doom2+psxtc+psxtcmus.pk3 fine

(Not using psx doom customizer)
so far so good, no freeze.
Maybe I'll be able to "pin-point" the culprit (problem PK3/setting in gzdoom.ini)

Re: latest gzdoom freezes after a few minutes

by _mental_ » Fri Mar 01, 2019 9:14 am

According to the second dump, it was deadlocked in openal32.dll. Just out of curiosity, will it freeze with -nosound command line option?

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Fri Mar 01, 2019 9:07 am

The system is less than a year old, CPU and motherboard released less than 9 months ago. Are you really sure? What Component should I replace?

Maybe there's some kind of Debug mode in gzdoom? How can I collect Verbose logs or something? I cannot even get to "Send GZdoom crash report" stage.

Re: latest gzdoom freezes after a few minutes

by Graf Zahl » Fri Mar 01, 2019 9:03 am

Prepare to buy some new hardware soon. This sounds like some component in your system is coming close to the end of its lifespan.

Re: latest gzdoom freezes after a few minutes

by lafoxxx » Fri Mar 01, 2019 8:39 am

_mental_ wrote:As a quick check, could you please try to enable VSync? Also, why do you use legacy/vintage build with quite modern hardware?
VSync was enabled during previous attempts -- I disabled it (that's why it's off in the config), but it didn't make any difference. The problem occured regardless of VSync setting.

I think I have also tried QZdoom (renamed to GZdoom -- app changed its icon immediately thereafter) -- with same "results", so I guess that's why I decided to move on to Vintage builds.


UPD:
Same results using latest Modern build -- but now it froze after much less time -- like 2 minutes.
vsync enabled.


only crash dump created https://drive.google.com/open?id=1rwLjU ... 2nKDCfFIVH
no entries in App event log

taskmgr -- wait chain analysis -- gzdoom.exe is in deadlock.

gzdoom.exe (pid 12340) thread 14660
|_gzdoom.exe (pid 12340) thread 8740
.....|_gzdoom.exe (pid 12340) thread 14660
gzdoom.exe (pid 12340) thread 8740
|_gzdoom.exe (pid 12340) thread 14660
.....|_gzdoom.exe (pid 12340) thread 8740

Top