-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very unstable steam: self-closing popups and freezes #3360
Comments
This sounds like steamwebhelper is running slowly and timing out, which is a fairly common occurence. Especially if GL isn't working and it is falling back to llvmpipe. |
That makes sense... GL should work, as the terrain benchmark ran at 290fps... any ideas what I can do to troubleshoot? |
Seems that the main issue is the file dialogue, which crashes every time... if I don't kill it, it will close with a stack smash protector message... How can I troubleshoot this? |
Steam has switched over to using whatever native file dialog is available. I personally get a gnome dialog and haven't had issues with it crashing. Could be you're using a kde dialog or something? |
Unfortunately, that is not the case. I'm using GNOME, so I'm definitely not using a KDE dialogue... I gave 6GiB memory to the VM, could that be a limiting factor? I only have 8 physical... |
Maybe? Giving it some swap space could help. FEX still has some memory usage optimization that it needs to do. |
I do have a dynamic swap on the host, and what's even more weird is that during the crash, I usually do not exceed 4-5 gigs of usage. Is there a way I could increase the stack size for the applications? |
This is not a FEX bug. |
Currently running FEX on krunvm, which in turn is running on Asahi Fedora Remix (GNOME), hardware is an M1 13' MacBook Pro w/ 8GiB RAM and 256GB SSD.
When I try running steam, it's very hit & miss, but I managed to see some patterns in the seemingly neverending issues:
I'll be happy to provide any additional info I might've missed.
The text was updated successfully, but these errors were encountered: