-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
CPU at 100% in menu in Vulkan on Linux #19131
Comments
Small clarification, it's not just in menus but everywhere at all times with the Vulcan backend, menus and games, a CPU core is being pushed to 100%, which core it is can switch while running. |
Like @foxsevent said, it's on the menu of PPSSPP AND also in game, tested with Tekken 6, Medal Of Honor Heroes and PES 6, one core is locked at 100% for no apparent reason and the core used can change at any time. Here is my specs and PPSSPP info : |
Starts after Some renaming, add a bunch of sanity debug-asserts . |
Thanks, that's interesting! |
Hm, in my testing, I'm seeing 100% CPU in commits before that one. I'll bisect myself (maybe it's a different cause..) |
Alright, I've figured this out as far as I can tell. When I switched the SDL build to run independently of the message pump in Vulkan mode, I forgot to switch from SDL_PollEvent to SDL_WaitEvent. So without being throttled by rendering, it'll just spin. There seems to be some differences in behavior to iron out but once that's done, this will be fixed. The starting commit mentioned by PhantomX above doesn't seem to have anything to do with it.. |
As it says on the tin.
Reported to happen on NVIDIA by KickMeElmo on the discord.
The text was updated successfully, but these errors were encountered: