search

batocera-linux / batocera.linux

batocera.linux
https://batocera.org
Other
2.02k stars 515 forks source link

GZDoom Fails to Launch Games #10289

Open chewvodka opened 1 year ago

chewvodka commented 1 year ago

Batocera build version

Stable Official Release v38 (38oc 2023/10/14 21:43)

Your architecture

Atari VCS - x86_64

Your Graphic Processor Unit (GPU)

Integrated (e.g. Intel HD 550; RX Vega 8)

Graphical brand

AMD

Issue description

As per request from maximumentropy (@n2qz) in the Discord Channels...

GZDoom fails to load games on my system. It's an Atari VCS with embedded graphics (CPU AMD Ryzen Embedded R1606G with Radeon Vega Gfx, 4 cores, 2600 MHz)... All wad's tested appear to crash back to ES.

Expected result

Expected to have the games load up and be playable. Instructions are to essentially drop wad's into folder and launch from ES without any special configurations needed.

Reproduction steps

May be specifically limited to my hardware, as maxiumumentropy (@n2qz) was unable to reproduce...

  1. Place appropriate wad files into /userdata/roms/gzdoom folder. -> Attempting with full Doom 1. Tried renaming doom.wad to doomu.wad. Also tried placing into /gzdoom/UltimateDOOM folder. MD5SUM - C4FE9FD920207691A9F493668E0A2083
  2. Refresh gamelists to have the wad appear in ES.
  3. Launch said wad from ES
  4. RESULTS - Long lag on ES loading screen then crash back to ES without ever seeing GZDOOM load.

Logs and data

es_launch_stderr.log - https://pastebin.com/Y7Vj5FPP es_launch_stdout.log - https://pastebin.com/e2gWfAQp gzdoom.log - https://pastebin.com/pgk7y4Wr

Also relative dmesg log info:

[ 282.398901] [ 2596] 0 2596 7515414 7265284 58671104 0 0 gzdoom [ 282.398903] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=gzdoom,pid=2596,uid=0 [ 282.398928] Out of memory: Killed process 2596 (gzdoom) total-vm:30061656kB, anon-rss:29060752kB, file-rss:0kB, shmem-rss:384kB, UID:0 pgtables:57296kB oom_score_adj:0 [ 284.704151] oom_reaper: reaped process 2596 (gzdoom), now anon-rss:0kB, file-rss:0kB, shmem-rss:112kB

Appears to be a memory leak issue.

n2qz commented 1 year ago

System has 32G RAM. I think anon-rss:29060752kB indicates excessive allocation for reasons that aren't clear.

chewvodka commented 1 year ago

Possible workaround -> I renderer to Vulcan inside ES, game launched....

dmanlfc commented 1 year ago

i tested 32gb on my PC, i didn't see the problem with OpenGL. @chewvodka I have updated the build for the next v39 butterfly.

dmanlfc commented 1 year ago

@chewvodka try GZDoom from this v39 image here: https://drive.google.com/drive/folders/1_bqmR7CoZ78i7DolYt5b-RRqB5c-LPyN?usp=drive_link

dmanlfc commented 12 months ago

@chewvodka can we close this one?

chewvodka commented 11 months ago

As of 11/10, the build with the AMD/DRM fix, the problem still existed. Fixed by switching renderer to Vulcan.

Upgraded to dev-09eadd8af8 2023/11/14 17:36 - Problem still exists.

dmanlfc commented 11 months ago

@chewvodka as per Discord. Take your issue to the GZDoom developers. They'll likely give some advice as I could not duplicate this but I do t have the same HW.