You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.
Describe the Bug
Whenever you're running the application and it suddenly crashes (whatever the reason may be) it will cause a slowdown on the operating system, the O.S will be like this until the process it's completely closed.
Observation: I was playing Bloodborne when this happened.
Reproduction Steps
Open the application
Play any game
Wait for it to crash
Notice that windows will be slow until the process it's closed
Expected Behavior
The emulator crashing shouldn't cause a slowdown on the operating system.
Specify OS Version
Windows 11 24H2
The text was updated successfully, but these errors were encountered:
This seems like a "Please make the robbery go smoother" type of request 😅
It's better to focus on fixing the crash, rather than making the crash after-experience better. It would probably be simpler too. This issue also seems a bit too broad. Not every game crashes in the same way and for the same reason. If a game crashes due to a memory leak, then perhaps the whole system would be affected, just like in your case. But if it crashes due to some emulation inaccuracy, it would crash without hogging any resources, so it likely wouldn't affect the rest of the system.
Checklist
Describe the Bug
Whenever you're running the application and it suddenly crashes (whatever the reason may be) it will cause a slowdown on the operating system, the O.S will be like this until the process it's completely closed.
Observation: I was playing Bloodborne when this happened.
Reproduction Steps
Expected Behavior
The emulator crashing shouldn't cause a slowdown on the operating system.
Specify OS Version
Windows 11 24H2
The text was updated successfully, but these errors were encountered: