Created attachment 130460 [details]
Output of the game execution logged with script
The Game Valhalla Hills crashes for me on Mesa 17.0.2 on Archlinux.
I tried the mesa packages from the standard archlinux extra repo.
To get a little bit more information I added the line '--enable-debug \' to ./configure in the mesa_archlinux_package_source_files and created the packages and installed the packages mesa and mesa-vdpau, except from builded with enabled debug these packages are the same as from the standard archlinux extra repo.
The attached file run is the output of executing:
ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose ./ValhallaHills-Linux-Shipping
The attached file gdb is the output of executing:
ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose gdb ./ValhallaHills-Linux-Shipping
I also tried to play with MESA_GL_VERSION_OVERRIDE (the game seems to need at least 3.2) and MESA_GLSL_VERSION_OVERRIDE (the game seems to need at least 150) but with no effects on the error outputs.
The game works very well when using the amdgpu-pro driver version 16.60.379184 and turning off vsync in the game options. But I want to keep Mesa because of the need to downgrade packages for amdgpu-pro and bad performance on Grid Autosport.
The game also works with an old nvidia GeForce GT240 in my old PC in my cellar with both nvidia version 340 and mesa nouveau driver, with colour and blinking light issues but quite playable.
Created attachment 130461 [details]
gdb output of running and backtracing the game logged with script
Created attachment 130462 [details]
Created attachment 130463 [details]
Created attachment 130464 [details]
Created attachment 130465 [details]
Source files packagecreation archlinux with enabled debug
Thanks for this very nice report. :)
I can reproduce the issue with mesa/LLVM from today.
valgrind might give more information.
Created attachment 130515 [details]
valgrind output of the game execution logged with script
Thanks for your replies, I ran valgrind with:
ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose valgrind --error-limit=no ./ValhallaHills-Linux-Shipping
Please let me know if there are other options which could be useful to get better information.
Created attachment 130633 [details]
valgrind output with less missing debug info
Because I saw there is very much missing debug info in the first valgrind file I recompiled the affected libs with debug symbols.
The new valgrind file was generated with this line:
ST_DEBUG=tgsi MESA_DEBUG=1 LIBGL_DEBUG=verbose valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes --error-limit=no ./ValhallaHills-Linux-Shipping
This problem affects me as well on mesa 17.04 and llvm 4.0.0-1 with AMD RX 480. Any ideas what causes this problem?
We can't expect a patch from the developer since the studio doesn't exist anymore. For some reason proprietary AMD and nVidia drivers do work.
The crash at startup can no longer be reproduced. I have just tested with Mesa (4eb0411ed72) and LLVM (9031fd91990). Though, it still crashes with Mesa 17.1.0 and LLVM 4.0.0.
Can you upgrade LLVM and confirm, please?
(In reply to Samuel Pitoiset from comment #11)
> Hi there,
> The crash at startup can no longer be reproduced. I have just tested with
> Mesa (4eb0411ed72) and LLVM (9031fd91990). Though, it still crashes with
> Mesa 17.1.0 and LLVM 4.0.0.
> Can you upgrade LLVM and confirm, please?
I can confirm it is now working with current mesa-git and llvm-svn with both radeon and amdgpu driver.
Thanks for your work.
Thanks for fixing! With the current mesa-git and llvm-svn it seems to work flawlessly!
Game is crashing again with current git mesa/llvm reopening.
mesa 18.0.0 / LLVM 6.0.0 has been reported as failing also.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1263.