We have found out that, when this triggers, it only happens when moving the mouse, I'll be posting a video soon.
DXVK does not interact with mouse input in any way, I strongly doubt it's even remotely possible that this is our bug.
Also haven't seen anything like this on my machine even in extended play sessions. As for Unreal Engine titles, I ran Hellblade and Days Gone for ~an hour not too long ago to test some unrelated changes.
DXVK does not interact with mouse input in any way, I strongly doubt it's even remotely possible that this is our bug.
Also haven't seen anything like this on my machine even in extended play sessions. As for Unreal Engine titles, I ran Hellblade and Days Gone for ~an hour not too long ago to test some unrelated changes.
I understand that they don't interact with mouse input, but when I run a game that natively uses Vulkan (ie. Quake 2 Remastered, Saints Row) they're not affected by this problem.
Switching to any of your releases paired with a vkd3d release completely fixes this mouse problem. I'm not any more expert than you, but the only thing dxvk and vkd3d have in common is dxgi.
I don't know if I'm being helpful but I can post a video on YouTube or logs.
Well what I'm saying is that this functionally doesn't make any sense and I can't reproduce it.
First step would probably be to provide detailed info about your build environment, including compiler version, MinGW version if applicable, and the exact command lines you're using to build the whole thing.
Another question would be what kind of environment you're running on as well, any sort of input issue points more towards wine/compositor issues than us.
Well what I'm saying is that this functionally doesn't make any sense and I can't reproduce it.
First step would probably be to provide detailed info about your build environment, including compiler version, MinGW version if applicable, and the exact command lines you're using to build the whole thing.
Another question would be what kind of environment you're running on as well, any sort of input issue points more towards wine/compositor issues than us.
I'm using fully updated Arch Linux, MinGW 13.1.0-1.
I tried with X11, X11 + gamescope, Wayland and Wayland + gamescope. Same problem happens after roughly 25 to 40 minutes of gameplay.
There's an intermittent heavy stutter that runs at its own pace, but only when playing with keyboard and mouse apparently, and it gets worse if you move your mouse once the "timebomb" triggers.
I'm using your package-release.sh script to build dxvk, using vkd3d's package-release.sh script to build vkd3d as well. Nothing goes wrong while compiling. Switching to "old" versions of vkd3d + dxvk completely gets rid of the issue.
Running a game that natively uses Vulkan or OpenGL never triggers this problem (under the same proton prefix and under the same circumstances of course).
I'm going to upload a video of the problem on YouTube (recorded by a friend of mine) in order to showcase the problem.
Video uploaded, manually switch to 1080p if it starts at 360p. This is a footage after roughly 30 minutes of playtime. The lag "timebomb" shows up at 0:44 timestamp:
Does this also happen with the builds that ship with Proton Bleeding Edge or downloaded from GitHub CI or only with self compiled?
Also are you able to bisect which commit it started with?
I'm using fully updated Arch Linux, MinGW 13.1.0-1.
This is precisely what the release builds are from. MinGW stuff hasn't been updated in a year or so, so the past couple of stable releases were compiled using exactly this in release mode.
Switching to "old" versions of vkd3d + dxvk completely gets rid of the issue.
Does "old versions" include self-compiled builds of stable releases?
I'm not running anything special here, just plain old KDE Wayland with (generally) no Steam overlay and (generally) no Gamescope, and RADV on a 6900XT. If this is an issue that supposedly affects any (UE4) game on any setup then what exactly is it that makes my system the special snowflake that this doesn't happen on?
Sorry for the rather annoyed tone but we have a release planned soon, so if this issue actually does affect a majority of users then I need a reliable way to reproduce it in order to actually do somehting about it.
I'm using fully updated Arch Linux, MinGW 13.1.0-1.
This is precisely what the release builds are from. MinGW stuff hasn't been updated in a year or so, so the past couple of stable releases were compiled using exactly this in release mode.
Switching to "old" versions of vkd3d + dxvk completely gets rid of the issue.
Does "old versions" include self-compiled builds of stable releases?
I'm not running anything special here, just plain old KDE Wayland with (generally) no Steam overlay and (generally) no Gamescope, and RADV on a 6900XT. If this is an issue that supposedly affects any (UE4) game on any setup then what exactly is it that makes my system the special snowflake that this doesn't happen on?
Yes, to also answer @Blisto91 the "old versions" included my own self-compiled. I have self-compiled versions of both dxvk and vkd3d saved, but I don't know where to start, honestly, maybe we can guess something:
For the sake of having a complete background, I'm actually going to test this whole thing without using ecores on intel and by using only one ccx on amd. It's probably unrelated and nonsensical but it doesn't harm me to test, my boyfriend is also testing with me. We've been trying to troubleshoot this for days to no avail.
could you send a log with DXVK_LOG_LEVEL=debug
also could u try windowed mode
could you send a log with
DXVK_LOG_LEVEL=debugalso could u try windowed mode
Yes, I'll attempt both things after testing the ecores/ccx thingy.
Edit: I'm sorry because these tests take a very long time, it's 25 to 40 minutes per-test. Yet, reproducibility should be easy (not timewise of course) as long as you're playing with a mouse and a keyboard on newly compiled dxvk + vkd3d.
Can you try https://github.com/doitsujin/dxvk/tree/no-occlusion?
could you send a log with
DXVK_LOG_LEVEL=debug
also could u try windowed modeYes, I'll attempt both things after testing the ecores/ccx thingy.
Edit: I'm sorry because these tests take a very long time, it's 25 to 40 minutes per-test. Yet, reproducibility should be easy (not timewise of course) as long as you're playing with a mouse and a keyboard on newly compiled dxvk + vkd3d.
funny story, I can't reproduce it either
Can you try https://github.com/doitsujin/dxvk/tree/no-occlusion?
I'm building it while my boyfriend is testing without ecores.
could you send a log with
DXVK_LOG_LEVEL=debug
also could u try windowed modeYes, I'll attempt both things after testing the ecores/ccx thingy.
Edit: I'm sorry because these tests take a very long time, it's 25 to 40 minutes per-test. Yet, reproducibility should be easy (not timewise of course) as long as you're playing with a mouse and a keyboard on newly compiled dxvk + vkd3d.funny story, I can't reproduce it either
Is it actually git cloned and compiled or just picked from releases? If nobody can reproduce this here, it could actually be related to a change that affects ecores (to-be-confirmed since my boyfriend is still testing, he's playing since 31 minutes without the problem triggering as of now).
For the sake of having a complete background, I'm actually going to test this whole thing without using ecores on intel and by using only one ccx on amd. It's probably unrelated and nonsensical but it doesn't harm me to test, my boyfriend is also testing with me. We've been trying to troubleshoot this for days to no avail.
Does not seem to be the problem. Will try no-occlusion straight away @doitsujin
Can you try https://github.com/doitsujin/dxvk/tree/no-occlusion?
Timebomb triggered at 33 minutes with this fork. Some walls and corners were invisible. My boyfriend will test this again with debug logging, I'm going to sleep soon. Make a list of more things that I should try and I'll do it right after waking up (I don't have work so I'm free the whole day).
Well, that rules out the only DXGI change since 2.4.1, so....
Well, that rules out the only DXGI change since 2.4.1, so....
Could it be a shared change between DXVK and VKD3D? Because we don't experience that problem with neither Proton GE and Experimental, yet we used to not have that problem at all and I always compiled the latest git releases for both of us.
I strictly believe that, at some point in time, something changed, and it affected both dxvk and vkd3d, and specifically "mouse handling" (probably not the right term) somehow.
It's weird that anything that runs on native API (Vulkan / OpenGL) does not suffer from this issue on any Proton prefix, yet the moment we try using git compiled dxvk + vkd3d this starts triggering.
It's interesting that games that run, for example, on Insomniac Engine and its forks, don't even suffer from this issue, while other games (notably Unreal Engine) have this timebomb as long as they use DXVK or VKD3D and as long as you play them with a mouse and keyboard.
My boyfriend will provide debug logging until the problem starts happening, and if you can 100% conclude that this is certainly not a DXVK + VKD3D issue, I'll have to look somewhere else. Most worrying scenario would be this problem affecting the majority of people but they have no idea. We really need more people testing this.
Been playing Hogwarts Legacy for around 110 mins now but haven't been able to reproduce.
Proton Experimental Bleeding Edge (the beta branch), Ryzen 7950x, RTX 4080 (driver is 565.57.01), KDE X11, Steam overlay turned on and even obs open in the background.
Been playing Hogwarts Legacy for around 110 mins now but haven't been able to reproduce. Proton Experimental Bleeding Edge (the beta branch), Ryzen 7950x, RTX 4080 (driver is 565.57.01), KDE X11, Steam overlay turned on and even obs open in the background.
That's not exactly the steps, I meant manually compiling dxvk and vkd3d straight away and putting them in a compatibility tool.
I asked above if the issue shows with the builds included in Proton Bleeding Edge or from the CI.
Edit: Could you share the ones you have compiled?
I asked above if the issue shows with the builds included in Proton Bleeding Edge or from the CI.
This will take a long time to test, I was mainly testing git compiled dxvk and vkd3d. Bleeding Edge breaks too much stuff, I'd rather live with the lag timebomb.
I would like to try the ones you have compiled yourself to test with. Just package them up and attach here
I would like to try the ones you have compiled yourself to test with. Just package them up and attach here
I've got to sleep now, I'll keep myself updated when I wake up. File attached in the previous message.
Played Hogwarts Legacy for 90 minutes more, this time with the Bleeding Edge DLLs replaced with vkd3d-proton, dxvk and dxvk-nvapi from your archive. Still nothing sadly
since you can build your own dxvk and know that the issue has been happening for 2 months, could you bisect it?
Played Hogwarts Legacy for 90 minutes more, this time with the Bleeding Edge DLLs replaced with vkd3d-proton, dxvk and dxvk-nvapi from your archive. Still nothing sadly
My boyfriend actually tried experimental bleeding edge overnight (without my DLLs) and the timebomb triggers there as well. Are you sure you were actually playing with a keyboard and a mouse? The problem only seems to happen when using m+k. Regular Proton Experimental is completely fine and unaffected by the way. And again: native Vulkan/OpenGL games running under any of these compatibility tools do not expose the problem, so it's definitely a dxvk+vkd3d thing.
since you can build your own dxvk and know that the issue has been happening for 2 months, could you bisect it?
See my message above where I list my older compiled dxvk+vkd3d combos, I don't know where to start. If you have an idea, maybe a date, I can start from there and test.
You say affected games mostly use Unreal Engine. Did you reproduce it with non-UE games? When you say, you don't have this issue with OpenGL/Vulkan, again those probably don't use UE?
Moving the mouse in Wine/Windows has the side-effect of changing the timer resolution of the scheduler, to react quicker. I observed this behavior when using the default c++ stdlib Sleep() function instead of specific Windows targeted Sleep(), maybe something to think about.
Are you sure you were actually playing with a keyboard and a mouse?
Yes. I rarely play with anything else.
Let's try to get a bisect going even if we won't find the commit in one day. Just try to test with the builds i send when there is time.
Does the issue happen with this dxvk build? dxvk d85cabe4571fbc1862f5176f88feeaf49aa2f01f.tar.gz
Are you sure you were actually playing with a keyboard and a mouse?
Yes. I rarely play with anything else.
Let's try to get a bisect going even if we won't find the commit in one day. Just try to test with the builds i send when there is time. Does the issue happen with this dxvk build? dxvk d85cabe4571fbc1862f5176f88feeaf49aa2f01f.tar.gz
We will test this ASAP.
You say affected games mostly use Unreal Engine. Did you reproduce it with non-UE games? When you say, you don't have this issue with OpenGL/Vulkan, again those probably don't use UE?
Moving the mouse in Wine/Windows has the side-effect of changing the timer resolution of the scheduler, to react quicker. I observed this behavior when using the default c++ stdlib Sleep() function instead of specific Windows targeted Sleep(), maybe something to think about.
That is true, but how is it that it acts like a literal timebomb? AFAIK the problem should appear immediately.
Did you check your RAM and VRAM usage? When RAM/VRAM gets full over time, lags are usually the consequence.
Did you check your RAM and VRAM usage? When RAM/VRAM gets full over time, lags are usually the consequence.
They look fine, but this still doesn't exclude that there could be a leak somewhere (or memory management issues overtime), so you might have a point as well.
Are you sure you were actually playing with a keyboard and a mouse?
Yes. I rarely play with anything else.
Let's try to get a bisect going even if we won't find the commit in one day. Just try to test with the builds i send when there is time. Does the issue happen with this dxvk build? dxvk d85cabe4571fbc1862f5176f88feeaf49aa2f01f.tar.gz
Yes, it happened. I attached logs. When the timebomb ticked, he left the game open for further 40 seconds (still playing normally of course) before closing it.
Thanks!
Next build for when you have time: dxvk 899f48bc43a6e75f039cf999f1421bb8cccc571a.tar.gz
Thanks!
Next build for when you have time: dxvk 899f48bc43a6e75f039cf999f1421bb8cccc571a.tar.gz
We just tested regular Proton Experimental again without changing anything and the timebomb just happened there as well, it just took 1 hour instead of the usual 25-40 minutes. I'll be attaching logs here. Knowing that regular Proton Experimental shows this problem as well, should I still try that dxvk version? As before, the timebomb triggers and then the game lags only when moving mouse, there are literal fps drops as well, basically as shown in the last YT video I linked.
Which path should I take from now? The problem is affecting 3 different system by the way and we're crushing our heads on the wall trying to understand what's wrong. We can run Vulkan games for 6 hours straight on the same compatibility tools (GE, LFX2, Experimental, etc.) and this timebomb NEVER triggers
Here are Proton Experimental logs if you can make use of them:
game_dxgi.log
game_d3d11.log
I'm so clueless at this point. Do I try the next build or do I take a different path?
Edit note just to reiterate: some games are not affected, like Horizon Zero Dawn Remastered, Ratchet: Rift Apart, Saints Row The Third Remastered and some more games are NOT affected by this, somehow. It's mainly Unreal Engine games that seem to be problematic and have this weird lag timebomb after X minutes.
Thanks!
Next build for when you have time: dxvk 899f48bc43a6e75f039cf999f1421bb8cccc571a.tar.gzWe just tested regular Proton Experimental again without changing anything and the timebomb just happened there as well, it just took 1 hour instead of the usual 25-40 minutes. I'll be attaching logs here. Knowing that regular Proton Experimental shows this problem as well, should I still try that dxvk version? As before, the timebomb triggers and then the game lags only when moving mouse, there are literal fps drops as well, basically as shown in the last YT video I linked.
Which path should I take from now? The problem is affecting 3 different system by the way and we're crushing our heads on the wall trying to understand what's wrong. We can run Vulkan games for 6 hours straight on the same compatibility tools (GE, LFX2, Experimental, etc.) and this timebomb NEVER triggers
Here are Proton Experimental logs if you can make use of them: game_dxgi.log game_d3d11.log
I'm so clueless at this point. Do I try the next build or do I take a different path?
Edit note just to reiterate: some games are not affected, like Horizon Zero Dawn Remastered, Ratchet: Rift Apart, Saints Row The Third Remastered and some more games are NOT affected by this, somehow. It's mainly Unreal Engine games that seem to be problematic and have this weird lag timebomb after X minutes.
You try the next build... Otherwise the idea of a bisect is useless
Thanks!
Next build for when you have time: dxvk 899f48bc43a6e75f039cf999f1421bb8cccc571a.tar.gzWe just tested regular Proton Experimental again without changing anything and the timebomb just happened there as well, it just took 1 hour instead of the usual 25-40 minutes. I'll be attaching logs here. Knowing that regular Proton Experimental shows this problem as well, should I still try that dxvk version? As before, the timebomb triggers and then the game lags only when moving mouse, there are literal fps drops as well, basically as shown in the last YT video I linked.
Which path should I take from now? The problem is affecting 3 different system by the way and we're crushing our heads on the wall trying to understand what's wrong. We can run Vulkan games for 6 hours straight on the same compatibility tools (GE, LFX2, Experimental, etc.) and this timebomb NEVER triggers
Here are Proton Experimental logs if you can make use of them: game_dxgi.log game_d3d11.log
I'm so clueless at this point. Do I try the next build or do I take a different path?
Edit note just to reiterate: some games are not affected, like Horizon Zero Dawn Remastered, Ratchet: Rift Apart, Saints Row The Third Remastered and some more games are NOT affected by this, somehow. It's mainly Unreal Engine games that seem to be problematic and have this weird lag timebomb after X minutes.You try the next build... Otherwise the idea of a bisect is useless
I was eating, sorry for the late response.
My boyfriend was now testing the game without gamescope and using regular Proton Experimental (not Bleeding Edge) to rule out a Proton Experimental + Gamescope combo glitch (probably useless, but he's 31 minutes in already so the timebomb should trigger in a very bit), then I'll proceed and let him place the next dxvk build and as always I'll provide results and logs ASAP.
For reference, we're always using the same game in order to obtain coherent results.
Once the timebomb triggers (25 to 40 minutes for Bleeding Edge and latest git dxvk+vkd3d on ANY proton version; 1 hour for unmodified Proton Experimental -> not bleeding edge <-), every keyboard input or mouse input causes the game to stutter regardless, you can clearly see it up on the mangohud overlay in the following video as well (ignore my boyfriend's voice if you can hear it):
https://www.youtube.com/watch?v=e_Qqgy3ET4M
Edit: Forgot to attach logs:
game_dxgi.log
game_d3d11.log
Thanks!
Next build for when you have time: dxvk 899f48bc43a6e75f039cf999f1421bb8cccc571a.tar.gz
Trying this build right away, I'll report back with logs.
Edit: My boyfriend is going to record the whole session with also mangohud's frametimes graph, and if the problem happens again I'll just post a video again with a lagless portion included. My boyfriend is also going to make a video with his phone, explain and show in detail what's happening. I will obviously include logs as always, additionally to the two videos.
Thanks!
Next build for when you have time: dxvk 899f48bc43a6e75f039cf999f1421bb8cccc571a.tar.gz
@Blisto91 Same issue.
Video: https://www.youtube.com/watch?v=Bl_ZIOmIY0k
Video with my boyfriend actually illustrating the issue when it triggers: https://www.youtube.com/watch?v=dHJmVYjw4zE
Logs:
game_dxgi.log
game_d3d11.log
No idea what to try next.
After extensive testing and troubleshooting, I've decided to take a step back from Linux gaming for the time being. While I'll continue using Linux for my professional work, I plan to revisit gaming only after a considerable period, perhaps in a few weeks or months, hoping these issues will be resolved by then.
This very specific problem has become quite frustrating. I've found out that this now seems to happen even with regular Proton 9. I've tested this across three different hardware configurations, including a complete system reinstall, and unfortunately, the same issue persists. What's particularly concerning is that this problem always happens across various setups, including a full AMD system, and remains present regardless of whether I'm using X11, Wayland, or Gamescope in both of them.
While I totally respect that others might not be experiencing these issues, my experience tells me that this is not possible. At this point, rather than continuing to waste time, I'll be stepping away until there's a proper solution from whoever caused this, whether that's from Arch Linux, DXVK/VKD3D, or other involved devs. It's particularly BAD to encounter identical issues even after a fresh installation across multiple systems with different configurations, it's just not right.
I appreciate your efforts, but for now, I need to take a break from this thing and wait until this is all resolved.
Consider me unsubbed from this issue.
PS I personally and genuinely don't actually believe anyone who says that this problem can't be reproduced. Nothing personal.
If this was an easy to reproduce problem, you'd find more post about it online in various forums. I've never seen any such reports though and also never experienced this issue myself.
If this was an easy to reproduce problem, you'd find more post about it online in various forums. I've never seen any such reports though and also never experienced this issue myself.
I have reinstalled Arch Linux from scratch and this happens out of the box. Full AMD system. It just takes 25-40-50 minutes of mouse and keyboard input to trigger it. No chance that it can't be reproduced. I'll be out for the time being until developers find a solution, maybe 2 or 4 weeks, and then check back. Either Arch Linux devs did a whoopsie or dxvk+vkd3d did a whoopsie, I'm tired of endlessly troubleshooting this problem that I can't get rid of. I just tested now after a clean install and KovaaK started stuttering after 42 minutes.
If it also happens with older Proton versions then i am going to guess that it is this old issue https://github.com/doitsujin/dxvk/issues/2371
It is something we have heard reports of from time to time (Source 1 games being an example) but it isn't something we have ever been able to reproduce on our setups, not for a lack of trying, so it is hard to debug.
The best guess is that there is some overlay involved that starts to act up after a while with dxvk E.g Steam overlay or similar. But it is hard to say without some proper debugging which would require a dev or tester reproducing it.
If it also happens with older Proton versions then i am going to guess that it is this old issue #2371 It is something we have heard reports of from time to time (Source 1 games being an example) but it isn't something we have ever been able to reproduce on our setups, not for a lack of trying, so it is hard to debug. A maybe guess is that there is some overlay involved that starts to act up after a while with dxvk E.g Steam overlay or similar. But it is hard to say without some proper debugging which would require a dev or tester reproducing it.
It happens even without any Vulkan layer attached and, after triggering, only lags when sending mouse/keyboard input. This is all I can say. I have just wasted time on fully reinstalling vanilla Arch Linux on a full AMD machine just to see the exact same issue happening again. Please check all the videos above.
I'll try the LD_PRELOAD method, but KovaaK is a VKD3D game by the way. I already mentioned that this problem happens in both DXVK and VKD3D, but NOT if the game uses Vulkan or OpenGL as API.
This whole issue popped out of nowhere and even a clean reinstall doesn't solve it.
If it also happens with older Proton versions then i am going to guess that it is this old issue #2371 It is something we have heard reports of from time to time (Source 1 games being an example) but it isn't something we have ever been able to reproduce on our setups, not for a lack of trying, so it is hard to debug. The best guess is that there is some overlay involved that starts to act up after a while with dxvk E.g Steam overlay or similar. But it is hard to say without some proper debugging which would require a dev or tester reproducing it.
If YOU cant debug it, maybe give advice to those already having the issue on how to debug it???
but NOT if the game uses Vulkan or OpenGL as API.
Does this include Windows games using those APIs like Doom 2016 or Eternal? Because otherwise it would be conceivable that this is a Wine issue.
but NOT if the game uses Vulkan or OpenGL as API.
Does this include Windows games using those APIs like Doom 2016 or Eternal? Because otherwise it would be conceivable that this is a Wine issue.
Vulkan games and OpenGL games running on any version of Proton don't have this problem. I and my boyfriend are experiencing this issue only in DXVK and VKD3D at the same time, everything else is completely fine under the same compatibility layers.
If YOU cant debug it, maybe give advice to those already having the issue on how to debug it???
Note that i am not a dev but "just" a tester.
There was actually a "stutter after 40min" issues that sounds similar caused by the steam overlay a long time ago: https://github.com/ValveSoftware/steam-for-linux/issues/7505
LD_PRELOAD= %command% would work around it by completely disabling the steam overlay. Not sure why this ancient issue would resurface now though, and why almost no one else seems affected.
There was actually a "stutter after 40min" issues that sounds similar caused by the steam overlay a long time ago: ValveSoftware/steam-for-linux#7505
LD_PRELOAD= %command%would work around it by completely disabling the steam overlay. Not sure why this ancient issue would resurface now though, and why almost no one else seems affected.
I have had this issue in the past where the frame pacing completly tanks after about the same time when using gamescope or mangohud for no reason
yes, better use dxvk overlay for these sort of tests, as you may as well run into a mangohud bug.
This happens even without any overlay. I'm currently testing with LD_PRELOAD="".
It's funny how this gets a "can't reproduce" tag when all it takes is a clean Arch Linux install.
maybe this bug needs high fps to trigger?
It's funny how this gets a "can't reproduce" tag when all it takes is a clean Arch Linux install.
I'm on Arch and can't reproduce it at all either, I think everybody is already trying their best and nobody is even dismissing your issue.
maybe this bug needs high fps to trigger?
Nope, also happens capped at 60 fps.
It's funny how this gets a "can't reproduce" tag when all it takes is a clean Arch Linux install.
I'm on Arch and can't reproduce it at all either, I think everybody is already trying their best and nobody is even dismissing your issue.
I maintained a professional tone until I clean reinstalled Arch Linux on a full AMD system just to see the same issue pop again. It's not really "my" issue when a clean distro installation doesn't get rid of the problem.
Maybe just tell me which distro both DXVK and VKD3D gurus suggest to use and I will install it.
I would really like to be able to try and reproduce the problem, trust me. But if we include the issue i linked above then i have tried several times through the years on probably 3-4 different setups by now, so i just really don't know what more to try.
Afaik all on the team use Arch (correct me if i am wrong)
I would really like to be able to try and reproduce the problem, trust me. But if we include the issue i linked above then i have tried several times through the years on probably 3-4 different setups by now, so i just really don't know what more to try. Afaik all on the team use Arch (correct me if i am wrong)
I'll be able to tell you whether the LD_PRELOAD="" method works in 20 minutes, either way.
btw I also use arch (and can't reproduce), and I guess if that LD_PRELOAD thing doesn't work you can maybe try profiling proton and to see what's going on. (I haven't done this before, so you will probably have to look through some documentation and figure it out)
also are you using radv or amdvlk
Believe it or not, using LD_PRELOAD="" actually fixed the problem for me, even when adding mangohud and OBS game capture to the vulkan layers through VK_LOADER_LAYERS_ENABLE. I'm more than 1 hour in playing KovaaK using Proton Experimental Bleeding Edge and it's still buttery smooth.
Now my question is, what is Steam LD_PRELOADING into the game then? I digged a bit and found nothing.
My theory is that this "Record your game" thing on Steam somehow injects even without your overlay being active. Would that explain this whole "timebomb" situation and the timing? This is just a theory, but, as far as I'm concerned, this whole thing really just started happening around the time they implemented this new feature. Even though it's disabled on my side, I think that's what was causing the issue.
I could probably close the issue but, if anything, I'd like to know what Steam sets LD_PRELOAD to when launching my games. Do you know a reliable way to do that? Plus, my bf really just wants to first see this with his own eyes.
Now my question is, what is Steam LD_PRELOADING into the game then? I digged a bit and found nothing.
Probably some stuff for steam input, which would maybe explain why it's related to mouse input. You can check what steam sets LD_PRELOAD to when a game is running by looking at /proc/$PID_OF_THE_GAME/environ.
I could probably close the issue but
Yes, but please open a new issue about it referencing this one over at https://github.com/ValveSoftware/steam-for-linux/issues
Now my question is, what is Steam LD_PRELOADING into the game then? I digged a bit and found nothing.
Probably some stuff for steam input, which would maybe explain why it's related to mouse input. You can check what steam sets LD_PRELOAD to when a game is running by looking at /proc/$PID_OF_THE_GAME/environ.
I could probably close the issue but
Yes, but please open a new issue about it referencing this one over at https://github.com/ValveSoftware/steam-for-linux/issues
This is the only entry showing in LD_PRELOAD when launching the game with default settings:
LD_PRELOAD=/tmp/pressure-vessel-libs-4PFQW2/${LIB}/gameoverlayrenderer.so
For reference, my Steam overlay is completely disabled.
What if you also manually disable steam input for the game? Maybe it also (intentionally or not?) loads the overlay stuff even if you disable it.
What if you also manually disable steam input for the game? Maybe it also (intentionally or not?) loads the overlay stuff even if you disable it.
Steam Input was already turned off because that game is an aim trainer, so I turned it off to not add useless layers on top of the game.
Yes, but please open a new issue about it referencing this one over at https://github.com/ValveSoftware/steam-for-linux/issues
I probably won't do it until tomorrow because I'm strained by all these days of troubleshooting and I just don't want to deal with more log grabbing and stuff. You can feel free to post an issue, or wait until I do it, it's the same to me.
I'm closing this specific issue because it's caused by Steam's LD_PRELOADs, thanks everybody who helped me find the culprit.
I will probably open an issue at https://github.com/ValveSoftware/steam-for-linux/issues tomorrow, but you can feel free to do so as well.
Actually, I just played overwatch 2 and did run into the same issue.
Actually, I just played overwatch 2 and did run into the same issue.
Were you able to fix it with the LD_PRELOAD method?
LD_PRELOAD="" %COMMAND%
If you need mangohud:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%
If you also need gamemode for some reason:
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%
(you still need gamemoderun for gamemode to actually trigger)
Haven't tried yet, but I'll probably play again today, have already setup LD_PRELOAD="" in the launch parameters.
I wonder how long this bug has been around, probably not for too long, since it's the first time I experienced it, but haven't been playing for a month or so previously.
Thanks for being persistent in trying to solve this issue, as it's definitely a rough one.
Haven't tried yet, but I'll probably play again today, have already setup LD_PRELOAD="" in the launch parameters. I wonder how long this bug has been around, probably not for too long, since it's the first time I experienced it, but haven't been playing for a month or so previously.
Thanks for being persistent in trying to solve this issue, as it's definitely a rough one.
For me, it definitely started around the same time Valve implemented the "Record your game" thingy on Steam. And yeah I would say I'm quite persistent with things when it's not my fault, probably due to the way my work environment is (where colleagues accuse each others of having broken some code all the time), kinda reflects to other things I do.
Ran into the same issue about 3 days ago as well - Thanks for the LD_PRELOAD fix!
When you say your overlay is completely disabled, how do you mean? Have you taken any steps for that other than using the UI option in the Steam client to disable the overlay?
When you say your overlay is completely disabled, how do you mean? Have you taken any steps for that other than using the UI option in the Steam client to disable the overlay?
Completely disabled through Steam's UI.
Thank you for this thread @SheMelody. I thought I was going bonkers for the last few weeks looking for whatever it may have been. As I experienced this on a number of different games but not all games.
I appreciate the effort you went through on this.
Can confirm I have also been experiencing the same issue, but only since upgrading to Fedora 41. Couldn't find anything online and was thinking I was going crazy. Thanks for making the thread.
Having the same issue, stuttering occurred in Saitsfactory. Thought it was gamescope but turning gamescope off didn't resolve it. Happened in DX12 and Vulkan mode. Disabled steam overlay. Switched from Proton Experimental to GE-Proton-9-16
It initially seems to have been resolved by adding LD_PRELOAD="" to my launch commands.
Went stuttering in Satisfactory every 30-40m on mouse input that required a reboot of the game, to playing for almost an hour and half last session after adding the command without issue (wasn't able to test further).
Setting LD_PRELOAD="" seems to introduce input lag for me in Borderlands 2
Alan Wake 2 too had been showing some weird mouse lags recently (past month) on both Nobara 40 and Mint 22. It happens only if at least 15 minutes has passed. It simply will not happen sooner. I noticed this issue here, and tried to run the game on Lutris to see if lags go away and it was definitely fixed. I did not use LD_PRELOAD workaround for neither Steam nor Lutris.
I never compiled anything though... playing with default Proton 9/Experimental versions on both Steam and Lutris. I shall now try other games on Steam to see if they too have this mouse lag bug after 30 mins (tried Remnant 2 yesterday but I always rage quit it before 10 mins passed, despite trying hard not to. Now going to try Empire of the Ants and possibly Hellblade 2).
Ah! And god of war Ragnarok also has this problem!!
Empire of the Ants also has this problem.
I had this issue with Guild Wars 2. I want to also add what temporary fixed the time bomb was using the release version of DXVK. However this was my experience 2 weeks ago, currently experiencing mouse lag immediately in GW2. The fix for the 40 min lag time bomb was to use a release version of DXVK, however the immediate cursor lag I'm experiencing now is unrelated to DXVK. The current lag I am experiencing is worse with outside Value tree's of Proton. I've tested Experimental and GE Proton versions which have a 5-10 fps drop moving the cursor, however Proton or Wine compiled without value tree's shows a bigger fps drop moving the cursor. Again want to state this was only for Guild Wars 2, and not other games.
I had relief knowing this issue was made clear when noticed in CS2 massive lag spikes after playing 30 min , warframe too when doing nothing but not in Space Engineers (maybe because crashes before experiencing this lag).
Testing currently
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%
I had relief knowing this issue was made clear when noticed in CS2 massive lag spikes after playing 30 min , warframe too when doing nothing but not in Space Engineers (maybe because crashes before experiencing this lag). Testing currently
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%
Did you mean Counter Strike 2 or Cities Skylines 2?
I seem to have a similar issue that after around 40-60 minutes of gameplay suddenly the game starts stuttering. Not sure if its this but Im gonna try LD_PRELOAD="" as well.
EDIT: Actually seems to have helped... no more stutters.
AMD Radeon 7900 XTX
AMD Ryzen 7950X3D
32GB DDR5 Ram
OS:
Archbased (CachyOS) Kernel 12.2
Plasma KDE 6.2
Wayland
Having same issue with Star Trek Online
Also happens in Path of Exile 2 with its Vulkan renderer, which would mean this is unrelated to dxvk?
I am seeing this also on Manjaro KDE running Fallout76 using GE-Proton9-20. The game runs perfectly smooth for about exactly 30 minutes or so then the jitter line in mangohud just goes crazy and the only fix is to restart the game.
Currently using this launch parameter:
gamemoderun mangohud %command%
I will try some of the above fixes and report back.
I can report that after over an hour it has not returned. The only thing added to the run command was LD_PRELOAD="" for a total command of:
LD_PRELOAD="" gamemoderun mangohud %command%
Mangohud works and so does gamemoderun without anything additional.
This was occurring to me in Path of Exile 2 with both DX12 and Vulkan.
With Steam overlay disabled, LD_PRELOAD="" did not work
With Steam overlay enabled, LD_PRELOAD="" worked
However, I did not test steam overlay enabled without LD_PRELOAD, so I cannot say whether that or enabling Steam overlay (or both) did the trick.
I am experiencing this in FarCry5. After almost exactly 27 minutes it occurs with a 4080 on 5900X at 5120x2160. Frametimes spike to 65ms in a sawtooth shape, from around 9ms.
LD_PRELOAD workaround works.
I had this issue with armored core 6 when I use gamescope to send it to my TV. But steam input doesn't seem to work as i can't use my controller with LD_PRELOAD in the launch command. Is there something I can do to force this?
Don't you need to add strings inside " " to point to which files to preload
otherwise it preloads nothing.
On Wed, Dec 11, 2024, 5:32 AM Jeremy @.***> wrote:
I can report that after over an hour it has not returned. The only thing
added to the run command was LD_PRELOAD="" for a total command of:
LD_PRELOAD="" gamemoderun mangohud %command%Mangohud works and so does gamemoderun without anything additional.
—
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2535867001,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUWVMVH5HECYUSU5WV22K32FAWG3AVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZVHA3DOMBQGE
.
You are receiving this because you commented.Message ID:
@.***>
Don't you need to add strings inside " " to point to which files to preload otherwise it preloads nothing.
…
On Wed, Dec 11, 2024, 5:32 AM Jeremy @.> wrote: I can report that after over an hour it has not returned. The only thing added to the run command was LD_PRELOAD="" for a total command of: LD_PRELOAD="" gamemoderun mangohud %command% Mangohud works and so does gamemoderun without anything additional. — Reply to this email directly, view it on GitHub <[#4436 (comment)](https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2535867001)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APUWVMVH5HECYUSU5WV22K32FAWG3AVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZVHA3DOMBQGE . You are receiving this because you commented.Message ID: @.>
The empty LD_PRELOAD prevents gameoverlayrenderer.so (both 32/64) from being loaded.
I add "/usr/lib/libgamemode.so" (64bit) Helps with gamemode than without
it.
On Wed, Dec 18, 2024, 8:35 AM jeisom @.***> wrote:
Don't you need to add strings inside " " to point to which files to
preload otherwise it preloads nothing.
… <#m_-7229722878671354874_>
On Wed, Dec 11, 2024, 5:32 AM Jeremy @.> wrote: I can report that
after over an hour it has not returned. The only thing added to the run
command was LD_PRELOAD="" for a total command of: LD_PRELOAD="" gamemoderun
mangohud %command% Mangohud works and so does gamemoderun without anything
additional. — Reply to this email directly, view it on GitHub <#4436
(comment)
https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2535867001>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUWVMVH5HECYUSU5WV22K32FAWG3AVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZVHA3DOMBQGE
https://github.com/notifications/unsubscribe-auth/APUWVMVH5HECYUSU5WV22K32FAWG3AVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZVHA3DOMBQGE
. You are receiving this because you commented.Message ID: @.>The empty LD_PRELOAD prevents gameoverlayrenderer.so (both 32/64) from
being loaded.—
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2551635444,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUWVMXDYLX4K2QEH7PBJQ32GGI43AVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRGYZTKNBUGQ
.
You are receiving this because you commented.Message ID:
@.***>
Just started following this thread. I have a similar issue:
It doesn't matter if I use Steam Overlay, mangohud, or vkbasalt. I always end up getting stutters around the 30 min mark.
I have played a few DX12 and OGL games 30-Min-Stutter does not kick in. I will play a few other games and see if the same problem happens outside of DX11 games.
I have not tried the LD_PRELOAD= yet. I will read up on this some more and see if it works.
I bought a new GPU because a few peeps from the Bazzite Reddit suggested my low VRAM 4GB GPU was causing issues. I got a 12GB 7700XT and got the same 30-Minute-Stutters. Tried different BIOS settings and same issue has been popping up for a while now.
Hopefully this gets sorted soon.
The thing is steamoverlay.so is used by steam for everything these days,
you just can't disable it from running.
Just make sure that overlay option is turned off in options.
That option actually is a preload option and most likely preloading
steamoverlay.so by default, and resolves issues for certain folks in
certain situations.
On Sun, Dec 22, 2024, 9:25 AM joranm1 @.***> wrote:
Also having this issue here.
That bug has been driving me crazy for some time now...
Thankfully LD_PRELOAD=" " %command% solves the issueThat Game Recording update is definitely broken
—
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2558509345,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUWVMSRLPF7VYBP63BXOXT2G3RWVAVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGUYDSMZUGU
.
You are receiving this because you commented.Message ID:
@.***>
The thing is steamoverlay.so is used by steam for everything these days, you just can't disable it from running. Just make sure that overlay option is turned off in options. That option actually is a preload option and most likely preloading steamoverlay.so by default, and resolves issues for certain folks in certain situations.
…
On Sun, Dec 22, 2024, 9:25 AM joranm1 @.> wrote: Also having this issue here. That bug has been driving me crazy for some time now... Thankfully LD_PRELOAD=" " %command% solves the issue That Game Recording update is definitely broken — Reply to this email directly, view it on GitHub <[#4436 (comment)](https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2558509345)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APUWVMSRLPF7VYBP63BXOXT2G3RWVAVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGUYDSMZUGU . You are receiving this because you commented.Message ID: @.>
Well, that's where things get funny:
Steam Overlay was already disabled in options because of https://github.com/ValveSoftware/steam-for-linux/issues/11479
Actually, I just played overwatch 2 and did run into the same issue.
Were you able to fix it with the
LD_PRELOADmethod?LD_PRELOAD="" %COMMAND%If you need mangohud:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%If you also need gamemode for some reason:
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%(you still need gamemoderun for gamemode to actually trigger)
Does anyone know if this will be fixed soon since I would really love to have the Steam overlay's browser so I can just search stuff up while I queue for Helldivers 2 matches (using this workaround disables the overlay)
Actually, I just played overwatch 2 and did run into the same issue.
Were you able to fix it with the
LD_PRELOADmethod?LD_PRELOAD="" %COMMAND%If you need mangohud:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%If you also need gamemode for some reason:
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%(you still need gamemoderun for gamemode to actually trigger)
Does anyone know if this will be fixed soon since I would really love to have the Steam overlay's browser so I can just search stuff up while I queue for Helldivers 2 matches (using this workaround disables the overlay)
Have you tried enabling the overlay while disabling GPU accelerated rendering in web views?
Tell us if it works for you
Actually, I just played overwatch 2 and did run into the same issue.
Were you able to fix it with the
LD_PRELOADmethod?LD_PRELOAD="" %COMMAND%If you need mangohud:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%If you also need gamemode for some reason:
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%(you still need gamemoderun for gamemode to actually trigger)
Does anyone know if this will be fixed soon since I would really love to have the Steam overlay's browser so I can just search stuff up while I queue for Helldivers 2 matches (using this workaround disables the overlay)
Have you tried enabling the overlay while disabling GPU accelerated rendering in web views?
Tell us if it works for you
That only delayed the inevitable and when it came, the issue was even worse
Just adding to the list the two games I have encountered this exact same issue in. Same symptoms: game runs absolutely perfect then suddenly starts stuttering and the frame times go out of whack. The stutter is constant while moving the mouse, and less frequent while moving the player character with WASD; no stutter when no user input is being provided, i.e. NPC and background animations, player character idle anim etc. all fine. Using keyboard and mouse, no gamepad.
LD_PRELOAD="" workaround solved it.I think I'm seeing this issue in Grey Zone Warfare, but instead of small stutters, it locks up almost entirely, and causes the amdgpu driver to timeout over and over until the entire system freezes up, or the game crashes.
(entire chunk of the following log here - the large time jumps are probably points I restart the game)
Dec 27 17:13:03 corais kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32793)
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: in process GameThread pid 209492 thread vkd3d_queue pid 209888)
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: in page starting at address 0x00008002cb6ea000 from client 10
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301030
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: MORE_FAULTS: 0x0
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: WALKER_ERROR: 0x0
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: MAPPING_ERROR: 0x0
Dec 27 17:13:04 corais kernel: amdgpu 0000:0b:00.0: amdgpu: RW: 0x0
Dec 27 17:13:13 corais kernel: traps: steamwebhelper[206896] trap invalid opcode ip:7f29d0ecabcf sp:7ffca7fc8da0 error:0 in libcef.so[66c9bcf,7f29ccbed000+a36d000]
Dec 27 17:13:14 corais kernel: amdgpu 0000:0b:00.0: amdgpu: Dumping IP State
Dec 27 17:13:14 corais kernel: amdgpu 0000:0b:00.0: amdgpu: Dumping IP State Completed
... (a lot of the same thing)
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32793)
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: in process GameThread pid 270525 thread vkd3d_queue pid 271334)
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: in page starting at address 0x000080023ac76000 from client 10
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00701030
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: MORE_FAULTS: 0x0
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: WALKER_ERROR: 0x0
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: PERMISSION_FAULTS: 0x3
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: MAPPING_ERROR: 0x0
Dec 27 17:53:13 corais kernel: amdgpu 0000:0b:00.0: amdgpu: RW: 0x0
Dec 27 17:53:24 corais kernel: amdgpu 0000:0b:00.0: amdgpu: Dumping IP State
Dec 27 17:53:24 corais kernel: amdgpu 0000:0b:00.0: amdgpu: Dumping IP State Completed
@DrymarchonShaun a GPU hang is a completely unrelated issue and also probably not a DXVK bug, more likely a driver bug. Report it here using the 'radeon vulkan' template https://gitlab.freedesktop.org/mesa/mesa/-/issues, also check out https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/docs/drivers/amd/hang-debugging.rst?ref_type=heads to gather more info.
@DrymarchonShaun a GPU hang is a completely unrelated issue and also probably not a DXVK bug, more likely a driver bug.
Hmm, alright. If that's the case, then I must have multiple things happening at the same time. I'm seeing a bunch of the symptoms described on the issue on the steam-for-linux repo that came about from and links to this issue, and the hangs seem to only happen when the steam overlay is loaded.
EDIT: Hangs are still happening with LD_PRELOAD="", must be something else.
None of these things seem to fix ffxvi s stuttering issues. But I have to
account for its poor optimizations of being a ported console game.
Star Trek Online however continues to experience stuttering issues after
running smoothly for 30-45 min even after applying these env variables.
On Sun, Dec 29, 2024, 3:18 AM DrymarchonShaun @.***>
wrote:
@DrymarchonShaun https://github.com/DrymarchonShaun a GPU hang is a
completely unrelated issue and also probably not a DXVK bug, more likely a
driver bug.Hmm, alright. If that's the case, then I must have multiple things
happening at the same time. I'm seeing a bunch of the symptoms described on
the issue on the steam-for-linux repo that came about from and links to
this issue, and the hangs seem to only happen when the steam overlay is
loaded.—
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2564677675,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APUWVMXSJU5YFFEDIUNKQI32H7EARAVCNFSM6AAAAABROFOZSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUGY3TONRXGU
.
You are receiving this because you commented.Message ID:
@.***>
This is insane. I have common launching script for all games, which deals with prime_run/gamemode/ kills launchers etc.
So I added
export LD_PRELOAD=""
unset LD_PRELOAD
Now ALL games are smooth like I updated PC for a million.
Valve should stop breaking things....
It's funny that this issue has existed for one year or more as far as I remember but people are still not understanding the nature of the issue.
I solved this infamous "28-min time bomb mouse moving stutter" by enabling steam overlay in CS2 (counter strike2). I ain't no programmer and don't know why it helped, but it's shocking to me that not only the bug has not been resolved till this day, but also no one seems to understand what's the source of the bug.
but also no one seems to understand what's the source of the bug.
Steam/ubuntu12_32/gameoverlayrenderer.so
Steam/ubuntu12_64/gameoverlayrenderer.so
Those are preloaded, 1 of them will print famous error in log. Because system is 32 or 64 and it tries both.
Any way, if someone never uses overlay (like me), then it is better to set it empty.
I just imagined ... what will happen if both can be loaded ? :) (for example system has multilib config). I guess they will fight each other => lag.
Yep, my bet is on 32 and 64 conflict each other when both are loaded:
[alex@mymsi 20:01:53 sfml_wrap]$ lsof /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
steam 203628 alex 77rR REG 259,4 349308 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
run60fps 206877 alex 77r REG 259,4 349308 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamemode_ 206879 alex 77r REG 259,4 349308 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
prime-run 206903 alex 77r REG 259,4 349308 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
reaper 206905 alex mem REG 259,4 349308 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
CrBrowser 207293 alex mem REG 259,4 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
CrGpuMain 207341 alex mem REG 259,4 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
CrUtility 207356 alex mem REG 259,4 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
CrRendere 207367 alex mem REG 259,4 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
CrRendere 207371 alex mem REG 259,4 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
CrUtility 207508 alex mem REG 259,4 3146492 /home/alex/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
[alex@mymsi 20:01:59 sfml_wrap]$ lsof /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
run60fps 206877 alex mem REG 259,4 320632 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
gamemode_ 206879 alex mem REG 259,4 320632 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
prime-run 206903 alex mem REG 259,4 320632 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
python3 207061 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
steam.exe 207075 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
wineserve 207091 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 207098 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 207103 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 207114 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 207129 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
svchost.e 207137 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 207269 alex mem REG 259,4 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
sleep 207729 alex mem REG 259,4 320632 3146509 /home/alex/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
Yep, my bet is on 32 and 64 conflict each other when both are loaded:
They should only actually load the correct version for the executable, not both. Easy to test, just set the LD_PRELOAD to one of them.
Yep, my bet is on 32 and 64 conflict each other when both are loaded:
They should only actually load the correct version for the executable, not both. Easy to test, just set the LD_PRELOAD to one of them.
Yep, in addition, steam itself (and all it's children processes) are "infected" by 32 bit library on 64 bit multi-lib system.
Yep, my bet is on 32 and 64 conflict each other when both are loaded:
Why it only happens after a certain time, e.g. for cs2 it's somewhat 28-min.
Whose fault is this? Steam or linux distro?
Yep, my bet is on 32 and 64 conflict each other when both are loaded:
Why it only happens after a certain time, e.g. for cs2 it's somewhat 28-min. Whose fault is this? Steam or linux distro?
It depends on the nature of the conflict. I also made chown root:root and cmod -r -w -x for that 32 bit library, so now Steam does not load any of them. Games just work and with good fps as it was 1-2 years ago.
If somebody needs browser overlay, it is better to setup OS keybindings (into DE config), it always overrides what game sets (at least for that DEs I used).
I've been able to reproduce this issue too on Fedora/KDE Plasma 6 (Wayland)/ProtonGE 9 22
So far only LD_PRELOAD="" seems to completely eliminate the problem, no severe stuttering after 40-45mins of gameplay.
I tried disabling GPU acceleration in web view without success.
It depends on the nature of the conflict. I also made
chown root:rootandcmod -r -w -xfor that 32 bit library, so now Steam does not load any of them. Games just work and with good fps as it was 1-2 years ago. If somebody needs browser overlay, it is better to setup OS keybindings (into DE config), it always overrides what game sets (at least for that DEs I used).
I tried changing uid/guid owner and chmoding ~/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so, steam overlay isn't loaded as expected but the issue remains.
Maybe i need to do that on the whole ubuntu12_32 folder?
Maybe i need to do that on the whole ubuntu12_32 folder?
Not sure, I had 32 and 64 bits loaded. So I did LD_PRELOAD. Then I checked again both libraries using lsof and found that 32 bit is still loaded by Steam on startup. So I just banned it until lsof stopped to show it loaded. Try whatever is best for you, confirm by the lsof.
I did both. Because LD_PRELOAD stops for new game launched and chmod cleanses startup of the steam.
Not sure, I had 32 and 64 bits loaded. So I did
LD_PRELOAD. Then I checked again both libraries usinglsofand found that 32 bit is still loaded by Steam on startup. So I just banned it untillsofstopped to show it loaded. Try whatever is best for you, confirm by thelsof. I did both. Because LD_PRELOAD stops for new game launched and chmod cleanses startup of the steam.
That's interesting, out of curiosity, i extended the scope of what was loaded and... this is quite confusing... i'll deep dive on it later to experiment.
lsof | grep -i overlay
gamescope 75862 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (path dev=0,50)
winedevic 76026 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76028 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76029 wine_sech slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76031 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76032 libusb_ev slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76033 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76034 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76035 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76037 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 76026 76040 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
steam 84305 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84316 SteamUpda slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84317 pool-spaw slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84318 gmain slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84319 dconf\x20 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84320 IOCP\x20T slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84321 gdbus slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84357 HTMLContr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84388 steam:cs0 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84389 steam:dis slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84390 steam:sh0 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84391 steam:sh_ slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84393 steam:tra slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84394 steam:tra slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84395 steam:tra slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84396 steam:tra slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84397 steam:gdr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84398 steam:gl0 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84409 IPC:CServ slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84414 IOCP\x20T slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84415 IPC:CStea slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84417 CFileWrit slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84424 SteamEngi slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84425 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84426 CHTTPCach slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84428 Controlle slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84429 CSteamCon slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84437 threaded- slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84439 CHTTPClie slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84441 CSystemMa slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84442 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84472 CFileWrit slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84477 threaded- slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84479 GamepadUI slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84482 SteamUIWa slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84490 IPC:CStea slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 84542 Steam\x20 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 85266 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 85272 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 85288 steam slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 85296 SocketThr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 85324 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 85955 CNet\x20E slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 86131 CHTTPClie slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 86147 CNet\x20E slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 86148 steam slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 87088 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 84305 87100 CJobMgr:: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87827 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87827 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87828 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87828 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87829 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87829 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87830 pool-spaw slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87830 pool-spaw slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87831 gmain slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87831 gmain slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87833 gdbus slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87833 gdbus slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87834 dconf\x20 slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87834 dconf\x20 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87835 gamesco:d slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87835 gamesco:d slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87836 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87836 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87851 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87851 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87852 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87852 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gamescope 87826 87854 gamescope slash mem REG 0,39 563100 /home/slash/.local/share/Steam/ubuntu12_64/steamoverlayvulkanlayer.so (path dev=0,50)
gamescope 87826 87854 gamescope slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87840 Xwayland: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87841 Xwaylan:d slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87842 Xwayland: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87843 Xwayla:sh slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87844 Xwayla:tr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87845 Xwayla:tr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87846 Xwayla:tr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87847 Xwayla:tr slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87848 Xwayland: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Xwayland 87839 87849 Xwayland: slash 102r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
Ysc_dx11. 88063 slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88065 wine_xinp slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88066 wine_sech slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88069 Ysc_dx1:d slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88070 Ysc_dx11. slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88071 Ysc_dx11. slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88072 dxvk-subm slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88073 dxvk-queu slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88074 dxvk-cs slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88076 dxvk-fram slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88080 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88081 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88082 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88083 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88084 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88085 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88086 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88087 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88088 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88089 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88090 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88091 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88092 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88093 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88094 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88095 dxvk-shad slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88097 WSI\x20sw slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88098 WSI\x20sw slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88100 Ysc_dx11. slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88108 audio_cli slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88109 audio_cli slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88110 wine_dsou slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
Ysc_dx11. 88063 88111 Ysc_dx11. slash mem REG 0,39 563091 /home/slash/.local/share/Steam/ubuntu12_32/steamoverlayvulkanlayer.so (stat: Operation not permitted)
this is quite confusing...
It is simple. Only 2 libraries are loaded there ;)
They're inherited. When Steam has loaded 32 bit library, anything it launches next (wine, proton, whatever script you have) - will have this library loaded + in addition proton loads 32 + 64 when it starts the game using LD_PRELOAD.
Indeed, i chown/chmoded the 32 and 64bits libraries and that fixed the issue, from there i tested keeping the correct 32bits overlay and that worked.
From the tests i've done so far (with a 32bits DX11 game)
I guess it's because a 64bits library is loaded with a 32bits game or the other way around (haven't tested it yet) causing this issue.
The question is why Steam is loading both at once... is it a normal behavior? What happens on a SteamDeck?
Could be a DXVK or PROTON issue as well not handling correctly these libraries with a 32bits or 64bits executable... (just a guess)
The question is why Steam is loading both at once... is it a normal behavior? What happens on a SteamDeck?
I can just speculate. As we see into LD_PRELOAD dump, it tries to load both. It has no sense if you know bitness. So this means, they didn't figure how to check current bitness and tried to load both. On plain Linux it would load 1 only though, because wrong bitness will fail unless you have multi-lib system.
That what I think.
But if you have stuttering with 1 loaded, then problem can be in library itself. For example, Windows has/had a "keyboard hook", that was a way to install the catch for any pressed key anywhere using DLL. And it had problem like here, if this hook was slow whole system was unresponsive. Probably they did the same for Linux to catch ctrl+tab. Any way, it is always bad idea to have any global hooks, I just removed it and don't bother. I admit though, voiding LD_PRELOAD may skip something useful in the future too.
On closer inspection, the culprit may be gamescope, i noticed that all 64bits gameoverlayrenderer.so are "not permitted" without it and with gamescope based on the 1st lsof i posted, one manages to be loaded by gamescope:
With gamescope, tries to load the 64bits one instead:
gamescope 75862 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (path dev=0,50)
...
Without gamescope, reaper (wine) loads the correct 32bits gameoverlayrenderer:
reaper 18456 slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (path dev=0,50)
Full lsof:
lsof | grep -i gameoverlayrenderer
steam 13174 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13185 SteamUpda slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13186 pool-spaw slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13187 gmain slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13188 dconf\x20 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13189 IOCP\x20T slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13190 gdbus slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13228 HTMLContr slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13257 steam:cs0 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13259 steam:dis slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13260 steam:sh0 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13261 steam:sh_ slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13262 steam:tra slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13263 steam:tra slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13264 steam:tra slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13265 steam:tra slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13266 steam:gdr slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13267 steam:gl0 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13278 IPC:CServ slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13279 IOCP\x20T slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13280 IPC:CStea slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13282 CFileWrit slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13284 SteamEngi slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13285 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13286 CHTTPCach slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13287 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13288 Controlle slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13289 CSteamCon slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13293 threaded- slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13294 CSystemMa slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13295 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13303 CFileWrit slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13312 threaded- slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13316 GamepadUI slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13321 SteamUIWa slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13340 IPC:CStea slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13390 Steam\x20 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13565 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13589 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13594 CNet\x20E slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13598 steam slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13636 SocketThr slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 13637 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 14260 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 14261 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 14808 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 14969 CNet\x20E slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 14970 steam slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 15291 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 16586 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 16587 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 16589 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 16825 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 16831 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 16835 CHTTPClie slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 17027 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 17099 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 17192 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 17212 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
steam 13174 17243 CJobMgr:: slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
reaper 18456 slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (path dev=0,50)
python3 18592 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
steam.exe 18594 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
steam.exe 18594 18658 steam.exe slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
steam.exe 18594 18664 steam.exe slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
wineserve 18596 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18601 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18604 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18608 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18614 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18626 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18632 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18637 services. slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
services. 18600 18647 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18606 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18607 wine_sech slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18609 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18610 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18611 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18635 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18603 18636 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18615 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18616 wine_sech slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18617 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18618 libusb_ev slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18619 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18620 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18621 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
winedevic 18613 18623 winedevic slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 18625 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 18625 18627 plugplay. slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 18625 18628 wine_sech slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 18625 18629 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 18625 18667 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
plugplay. 18625 18668 wine_thre slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
svchost.e 18631 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
svchost.e 18631 18633 svchost.e slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
svchost.e 18631 18634 wine_sech slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 18646 slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 18646 18649 rpcss.exe slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 18646 18650 wine_sech slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 18646 18651 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 18646 18652 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
rpcss.exe 18646 18653 wine_rpcr slash mem REG 0,39 563097 /home/slash/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18665 wine_xinp slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18666 wine_sech slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18669 Ysc_dx1:d slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18670 Ysc_dx11. slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18671 Ysc_dx11. slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18672 dxvk-subm slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18673 dxvk-queu slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18674 dxvk-cs slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18676 dxvk-fram slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18679 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18680 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18681 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18682 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18683 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18684 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18685 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18686 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18690 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18691 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18693 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18694 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18695 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18696 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18697 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18698 dxvk-shad slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18700 WSI\x20sw slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18701 WSI\x20sw slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18707 Ysc_dx11. slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18710 audio_cli slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18711 audio_cli slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18712 wine_dsou slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
Ysc_dx11. 18663 18713 Ysc_dx11. slash mem REG 0,39 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (stat: Operation not permitted)
gameoverl 18702 slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gameoverl 18702 18704 HTMLContr slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gameoverl 18702 18705 Screensho slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
gameoverl 18702 18706 Screensho slash 128r REG 0,50 353248 563077 /home/slash/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so
With gamescope, tries to load the 64bits one instead:
I don't have "gamescope" and still had a problem.
What you see there is inheritance, when binary starts new binary, that new one gets libraries of the parent loaded by the OS.
I have here complex chain of the bash scripts, which start bash and it has library, than this script restarts gamemode daemon for me and it gets library loaded too and so on.
Could be a wrong lead there for sure, i'll try to investigate while playing a bit more later, thanks for the help.
No, it's not gamescope.
As far as I understood, it's hanging within Steam's redirected input processing.
Just a heads up, the problem was confirmed to be related to the Steam for Linux, you should continue discussing it here: https://github.com/ValveSoftware/steam-for-linux/issues/11446
Although this problem doesn't seem to affect native APIs such as Vulkan and OpenGL, it's still not directly related to DXVK/VKD3D, although there's a correlation between gameoverlayrenderer.so and DXVK/VKD3D running under Proton.
Enabling Steam Overlay or else using a custom LD_PRELOAD statement such as LD_PRELOAD="" to preload nothing or LD_PRELOAD="something:something:something" to preload your things seems to completely workaround the problem. Steam Input will still continue to work.
The problem started happening since the game recording update for Steam.
Edit: Native Vulkan games (under Proton) seem to be affected as well, maybe not all of them.
Steam Input will still continue to work.
I have no idea what is it. So I would prefer to keep it completely removed in my setup. Thanks, though.
Steam Input will still continue to work.
I have no idea what is it. So I would prefer to keep it completely removed in my setup. Thanks, though.
You only need Steam Input for PlayStation / Nintendo gamepads and such. Usually, the "default" setting works just fine.
Although this problem doesn't seem to affect native APIs such as Vulkan and OpenGL
This is only correct for OpenGL. Native Vulkan games (running via wine) are affected as well.
Although this problem doesn't seem to affect native APIs such as Vulkan and OpenGL
This is only correct for OpenGL. Native Vulkan games are affected as well.
Yeah, I just saw some users having this problem on Vulkan, was never reported before and I never had them so I assumed it was fine.
I did run into this issue in Path of Exile 2 with its Vulkan renderer.
However the OpenGL game Slay the Spire was fine.
I don't get why they keep adding "features" which immediately break everything or make it worse. This one is not alone. They added GPU detection, which powers-on double gpu which raises heat and consumption just to keep steam opened, Had to block it by appguard.
The problem started happening since the game recording update for Steam.
Nah, this time-bomb stutter issue started long before. It has existed at least for more than a year. People reported it on CS:GO long long time ago, and the fix was similar: disable steam overlay or use 'LD_PRELOAD'.
for me LD_PRELOAD does nothing. and true that i had this time bomb before steam recording, however i only noticed it in CS2 and as i dont play CS2 for some few months, i havent tried to troubleshot this so cant confirm for sure is this related in any way.
Actually, I just played overwatch 2 and did run into the same issue.
Were you able to fix it with the
LD_PRELOADmethod?LD_PRELOAD="" %COMMAND%If you need mangohud:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%If you also need gamemode for some reason:
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%(you still need gamemoderun for gamemode to actually trigger)
Will mangohud workaround command be needed to work with
gamescope --mangoapp
why is this closed??
Because it isn't a dxvk bug.
Edit: A open issue about it can be found at the steam-for-linux repo https://github.com/ValveSoftware/steam-for-linux/issues/11446
My conscience has made me wake this issue up. I'm sorry. My conscience is doing this.
In my post above, I said I cannot play Remnant II for more than 10 minutes before Alt+F4ing it. The truth is, this game is actually very fun, it is me who sucks. I've been stuck at the last boss for more than a year now... this is why I keep rage quitting it fast, because I cannot handle the truth. That I suck at it. But this game is actually really fun... I was wrong to dishonor it.
I can finally sleep well.
We have found out that, when this triggers, it only happens when moving the mouse, I'll be posting a video soon.
Identical to what I see in OW2. Runs perfect for half an hour or so, then has issues.
While actually playing and moving myself, the game goes haywire, the symbol claims its lagging (but I see the same issue in Kovaaks which is offline) and it tries to claim its still 100 fps while it is chopping all over the place. But if it's playing a killcam (in the same game) it doesn't drop a frame. Moment i have control and move again it starts lagging.
Hopefully there will be no need for the empty LD_PRELOAD or forcing the user to use the steam overlay.
I wanted to report that I am also experiencing this issue now
It started this week with Borderlands 3 and now i get it today with Dishonored 2.
Im on Cachy OS, Kernel 6.14.5-3, Mesa 25.0.5, and tried the latest proton experimental and the latest Proton GE
This issue does not effect the steam deck
Actually, I just played overwatch 2 and did run into the same issue.
Were you able to fix it with the
LD_PRELOADmethod?LD_PRELOAD="" %COMMAND%If you need mangohud:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%If you also need gamemode for some reason:
LD_PRELOAD="/usr/lib/libgamemodeauto.so.0" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 gamemoderun %COMMAND%(you still need gamemoderun for gamemode to actually trigger)
Just if someone has problems with mangohud, the actual names of the overlay are
VK_LAYER_MANGOHUD_overlay_32_x86VK_LAYER_MANGOHUD_overlay_64_x86_64you can find your with vulkaninfo, if these don't work.
When adding LD_PRELOAD="" my controller does not work at all anymore
Someone experiencing the same thing?
When adding
LD_PRELOAD=""my controller does not work at all anymore Someone experiencing the same thing?
Yes, because main goal is turn off steam's support for inputs, like controller by doing this ;)
You can try to configure controller outside steam somehow.
proton experimentalx10 2025-05ge-proton9-20x1 2024-12DXVK_LOG_LEVEL=debug`x4 2024-11LD_PRELOAD=" " %command%x2 2024-12mangohud %command%x1 2024-12LD_PRELOAD="" gamemoderun mangohud %command%x3 2024-12gamemoderun mangohud %command%x1 2024-12
There's a literal "lag timebomb" when pulling the latest git versions of DXVK and VKD3D and compiling them. These lag timebombs are unified, meaning that they happen in both DXVK git and VKD3D git, and they trigger after roughly ~25 to ~40 minutes of gameplay and generally only trigger if the user is providing input to the game. This problem exists since roughly 2 months and I felt like it would be good to report it here. Since the problem is unified (happens on both DXVK and VKD3D) I actually didn't know where to report it.
Affected games mostly use Unreal Engine. Insomniac Engine games, for example, didn't seem to be affected.
Using a "Release" version of DXVK + a "Release" version of VKD3D seems to solve the problem.
More specifically, the game is smooth before the "timebomb" triggers, then consistent and repeated heavy stutters begin to happen. If needed, I can record a video.
EDIT: We have found out that, when this triggers, it only happens when moving the mouse.
Software information
Any game that uses DXVK or VKD3D pulled from git and compiled, this problem is unified and common in both DXVK and VKD3D
System information
Apitrace file(s)
Log files