-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Bug] #6802
Comments
I see that this has been an issue in the past, too, but following the steps posted in those threads does not solve my issue. As far as I can tell (based on my attempts to fix the issue), my only solution is to wait for an update that fixes the problem. |
If the emulator process can't be terminated then I'd say its an OS issue. IIRC there was some weird memory management related bug on Windows that would make the emulator hang for a long time while unmapping memory. Though personally I don't think I ever had this issue. |
Description of the issue
Ryujinx doesn't close when terminated via terminal, using the 'actions > Stop Emulation' menu, pressing 'x' to close the program, or when terminated manually via Task Manager. The program remains open and uses 0% CPU but 3.2 gigs of memory at any given moment until my computer is shutdown. Furthermore, to shut down my computer, I'm finding that I often have to hard boot my PC (because shutting down via Windows doesn't work if I've opened Ryujinx that session.) I've isolated this issue to Ryujinx and it's really quite frustrating. I've stopped myself posting several times because an update has released, but the issue has not been fixed despite three recent updates. I see that there's another one today, but I'm not optimistic it will fix the issue.
Reproduction steps
Opening Ryujinx to play (in my case, Tears of the Kingdom), then attempting to terminate the program.
Log file
Ryujinx_1.1.1298_2024-05-12_14-14-27.log
OS
Windows 11
Ryujinx version
1.1.1298
Game version
1.2.1
CPU
Ryzen 7 7700x
GPU
NVIDIA RTX 4070 Super
RAM
32 GB
List of applied mods
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: