-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Incredibly high RAM usage, possibly a leak? #3278
Comments
While I can't specifically comment on the supposed memory leak, I can supply you with some knowledge. Shader compile stutter (and really just full-on hanging sometimes) is completely normal, intentional even. When a game requests a shader that isn't compiled yet, execution must halt in order to have the proper effect apply to the scene. Alternatively, you can tick the "Asynchronous Shader Compilation" box in the GPU tab in settings. This should eliminate stutters at the cost of having effects apply in a non-standard way (such as objects popping in and maybe not looking too great for a while before the shader/effect applies). The quitting issue one you describe is one I experience as well on Linux. Not sure why, and I haven't looked into it personally. If you quit the emulator by going to File -> Exit, it exits perfectly fine though, so maybe try it out. |
Thank you for your reply and insights given, I'm aware of the shader compile stutter being normal, but completely freezing the emulator? I had to restart the game in question, Resident Evil Revelations 2, several times until more shaders compiled, and startup would of course take longer the more they compiled, but that's just my slow HDD at fault here I'm sure. I may give Asynchronous Shader Compilation a shot, I do enjoy some good debugging info anyway. As for the quitting issue, mine often doesn't exit properly until I use the task manager, with the process using around 2-3GB of my RAM until killed. I'd test this on Windows but I'd have no support for Vulkan there at all, but I am curious if OpenGL wouldn't cause crashes. Once again thanks. :) |
I came back to this just now and the emulator crashes right on startup, no errors or anything. The terminal closes too fast to tell what's wrong. |
Hello. I'm new to this emulator in particular now that I have a "more capable" setup, and I'd like to say thanks for the work done here! But back on topic, said setup includes:
While performance is pretty much perfect for the working titles, the emulator often crashes or at least hangs while compiling shaders, and memory usage keeps going up, eventually filling the whole RAM and even swap file. When quitting the game or emulator, the whole computer simply refuses to properly end the application for a good 10 minutes.
If I can do anything to contribute, I will. Thanks in advance.
The text was updated successfully, but these errors were encountered: