-
-
Notifications
You must be signed in to change notification settings - Fork 331
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
Stability Matrix is very slow to launch or doesn't launch after updating to V2.12.2.0 #960
Comments
I had to uninstall and down grade to version 2.12.0 in order for it to launch like it used to (less than a second). |
Update I tried updating it again to V2.12.3 and it does the same thing. I'll have to downgrade again back to 2.12.0 for the launcher to work fast like it did before. |
I have this same issue, but downgrading has not helped. Have not been able to use the app in8 weeks. Arch linux either standard kernel or Zen version, 3080 GPU |
Same issue, unable to upgrade. Any version between 2.12.0 and now fails to load at all. The process in task manager shows no memory usage, no cpu usage, does nothing. Rolling back again to 2.12.0 still works. |
@Genomerio try the aur/stabilitymatrix-git package, I found some issues causing slowdown with the others and it's loading within a few seconds for me now |
[dev to main] backport: adds the thing about the stuff (959)
Package
Stability Matrix Launcher
When did the issue occur?
Updating the Package
What GPU / hardware type are you using?
Nvidia RTX 4070TI
What happened?
After updating to V2.12.2.0 the launcher takes approximately 5 to 10 minutes to launch and sometimes it won't launch at all. I look on task manager and the Stability matrix app just sits there and does nothing. But when it does decide to launch it runs a bit sluggish then it runs normal. The previous version ran perfectly fine with no issues when launching.
Console output
Console would not load since the app wouldn't launch.
Version
V2.12.2.0
What Operating System are you using?
Windows
The text was updated successfully, but these errors were encountered: