Skip to content
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

Vulkan Async Sc thread takes 100% CPU when using OpenGL renderer #10443

Closed
linkmauve opened this issue Jun 11, 2021 · 3 comments · Fixed by #10463
Closed

Vulkan Async Sc thread takes 100% CPU when using OpenGL renderer #10443

linkmauve opened this issue Jun 11, 2021 · 3 comments · Fixed by #10463
Assignees

Comments

@linkmauve
Copy link
Contributor

Please do not ask for help or report compatibility regressions here, use RPCS3 Discord server or forums instead.

Quick summary

A thread named Vulkan Async Sc is taking 100% of one core despite not using Vulkan.

Details

Please describe the problem as accurately as possible.

0. Make sure you're running with settings as close to default as possible

  • Do NOT enable any emulator game patches when reporting issues
  • Only change settings that are required for the game to work

1. Please attach RPCS3's log.

RPCS3.log

2. If you describe graphical issue, please provide an RSX capture and a RenderDoc capture that demonstrate it.

N/A

3. Please attach screenshots of your problem.

N/A

4. Please provide comparison with real PS3.

N/A

5. Please provide your system configuration:

  • OS: ArchLinux
  • CPU: i7-8700k
  • GPU: R9 270X (a UHD630 is also present on the system and has a Vulkan driver, but is unused here)
  • Driver version: mesa master (21.2.0-devel commit a084e79a491)
  • etc.

Please include.

  • Anything else you deem to be important
    I was previously using the Vulkan backend when on the Intel card, before acquiring this R9 270X, so some settings might have carried over.
@Megamouse Megamouse added the Bug label Jun 11, 2021
@Megamouse
Copy link
Contributor

the log is inaccessible

@kd-11 kd-11 self-assigned this Jun 16, 2021
@kd-11
Copy link
Contributor

kd-11 commented Jun 16, 2021

I have the async scheduler thread only spawning when the vulkan renderer is being initialized, but I can reproduce this issue. Investigating.

@kd-11 kd-11 added the In Progress This issue is actively being investigated at the moment. label Jun 16, 2021
@kd-11
Copy link
Contributor

kd-11 commented Jun 16, 2021

It's triggered by automatic type management. I've added a thread early exit in case incompatible options are active. Fix will be available in the next PR.

@kd-11 kd-11 removed the In Progress This issue is actively being investigated at the moment. label Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants