Persistent crashes with cached shaders with Mesa #130
Comments
|
@matthew-cline I'm just a normal user not a linux expert and maybe wrong but, It seem i already install a require below on line 14. org.freedesktop.Platform/x86_64/18.08 system,runtime |
|
To fix the problem I tried locally emptying out all my installed flatpak stuff and the reinstalling flatpak Steam from scratch. First I had to install I'm using flatpak version 0.99.3 on Fedora 28 with KDE 5.13.3 |
|
Ping @valentindavid |
|
@matthew-cline are you installing Steam through command line or some GUI? |
|
@nanonyme Installed Steam via the flatpak command line. |
|
I wonder whether that migration case to newer runtime on upgrade just works poorly in flatpak currently |
|
It might be an issue with Mesa. I would recommend you to remove |
|
My hunch based on reading is Steam is having issues connecting to X11 in original report. The container should be letting connections through (that has not been touched) as long as context about what to contact to isn't missing. Does xrandr work inside the app @vibolvireak ? |
|
@nanonyme I may really happy to help if you provide more understandable guide on step by step how to perform your action because as i remark on my first comment that i'm just only a normal user so i don't know how to produce your step according to xrandr etc. Your question seem to be hard for me 😥 |
|
@vibolvireak What was the result of cleaning the mesa shader cache? |
|
@valentindavid @nanonyme sorry my bad after cleaning as you suggest with
Confirmed: now steam start fine no error and i can back to play my game. Thank you! |
|
I had this problem sometimes. But I always thought it happened with downgrading Mesa only (I have been switching version of runtime back and forth). But I suppose there is a real bug in Mesa here and we should try to reproduce it simply and report to upstream. There are probably others not using flatpak getting the same issue when upgrading distribution. I recommend we keep this issue open and we work on that. |
|
Hmm, that actually makes me wonder if it's even a good idea to persist the cache at all if it can result in this kind of issues. Of course currently it's speeding up game launches |
|
Could steam-wrapper cache the version of Mesa (both 32 and 64 bits) and cleans up the cache each time it detects a new version? |
|
I don't know but the logic would need to work in nVidia proprietary as well. Guess we could write some deployment timestamp in post install and track its changes in steam-wrapper? |
|
I guess that wouldn't in practice work except for these major runtime upgrades |
|
@vibolvireak do you happen to have Intel GPU? Looks like shader cache was only recently enabled there |
|
Then it was probably AMDGPU. I think it would be nice in general to clean the cache. And yes. The stamp is fine. With certain version of the kernel, you can get total gpu freeze when downgrading Mesa or LLVM. Never got that when upgrading though. We could use: |
|
Also "OpenGL core profile version string" |
|
@nanonyme @valentindavid I'm using Radeon RX 550. RemarkNo i can't play Dota 2.
When start the game the screen will look like this. I'm not yet test other game yet because i can't purchase it now. But i'm sure this will the mesa issue. |
|
@vibolvireak I do not have the same issue and I have a Radeon card. Are there any interesting messages in the console? If not, make it more verbose: |
|
You could also try:
|
|
@valentindavid |
|
If deleting shader cache again helps, I'm going to suspect there's something reproducibly breaking |
|
@vibolvireak Try to remove the cache again. If it does not work then, just reset.
Then run Steam again. |
|
Well remove Here is the error while starting dota 2 |
|
Try |
|
If disabling cache removes this noise, we can set that in the json. You can always set local override for it if you want it back on |
|
Finally running |
|
Iirc there was some way to make gdb follow forks as well |
bash-4.4$ gdb bin/linuxsteamrt64/dota2 core --batch --eval-command=backtrace
"/home/fedora/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/dota 2 beta/game/core" is not a core dump: Is a directory
No stack. |
|
Oh, right. There is a directory called core. What a silly idea. OK, then: Run the game it again. And then run |
|
Coming here from #163 I've started RimWorld and created a dump file and running the command from #130 (comment) I get this output. Is this worth anything here or should I attach this information to the bug with Mesa? |
|
Did you install SDK and debug as instructed couple of comments above? Without debug symbols the stack is reasonably useless |
|
Ah, sorry @nanonyme I completely missed that. Installing |
|
hmm, I've installed the missing flatpaks but the output from gdb seems to be the same with the new coredump |
|
Do I need anything extra installed on the host system? |
|
Did you run the flatpak with - - devel? I don't think you should need anything on host |
|
I ran |
|
Thanks. I don't have further pieces of advice, your stack just looks like gdb can't resolve symbols |
|
It looks odd. Can you please give us the output of |
|
There is no such file as |
|
Please run |
|
Wonder if deprecated extensions are getting properly removed |
|
I do not think this is the case here. The path points in the old .Platform. Extension would have different path. |
|
@vibolvireak does this still repro for you? |
|
@valentindavid @nanonyme @fooishbar I don't know what going on but now it's working really fine Today after away from computer for above 2 day and i start formating and install a fresh fedora linux again to my hard disk now i can start playing dota 2 really fine without changing any configuration thank everyone. :D |
|
|
If it's second, we might finally have a clue of what's going on |
|
@nanonyme Thank you feel free to close this issue |
|
Did you verify it reproduced without the numeric setting? |
|
Yes everything work out of the box click and play |
|
That's not what I asked. In terminal (outside Flatpak), type locale. Read numeric |
|
@nanonyme I hope i doing correctly but $ flatpak run --env=LC_NUMERIC=en_US com.valvesoftware.SteamSteam and dota 2 still working really fine. No problem |
|
Okay. Then it might be related to the cache flushing change instead. If you can no longer repro, may wish to comment on upstream ticket that properly flushing shader cache helped |
Environment
The text was updated successfully, but these errors were encountered: