Steam Game Recording is using a lot of CPU on an AMD Linux system. vainfo reports hardware encoding support, but Steam logs show VAAPI failing to create a device context before falling back to x264. What should I check, and is there a workaround?
Why is Steam recording using so much CPU on AMD Linux?
Answers
The log points to a VAAPI initialization failure, not simply a missing codec. Steam tries hardware encoding, fails to create the device context, then uses x264 on the CPU. That fallback would explain the jump in CPU usage.
vainfo showing encode profiles is useful, but it only confirms that VAAPI works in the context where you ran it. Steam may be running with different libraries, permissions, or environment settings. I wouldn't call it a Steam regression from this log alone.
Reply to this answer
First check how Steam is installed and launched, then compare that environment with the one where vainfo succeeds. In particular, look for access to the relevant /dev/dri render device and any VAAPI or library loading errors in Steam's logs. A sandboxed package can have different device access from a terminal session.
Also try a hardware encode in another application. If that works while Steam still fails, it narrows the problem toward Steam's runtime or configuration, though it doesn't prove which component is responsible.
Reply to this answer
For a workaround, try recording with another tool that can use VAAPI, such as OBS, and verify that its hardware encoder actually starts. If you need to stick with Steam's software fallback for now, reducing recording resolution or frame rate may make the CPU load more manageable.
Reply to this answer
Add your answer
Answers are reviewed before publication.
sidequestClerk+7M:
If you have more than one GPU, check which render device each application is using too. A successful vainfo result for one device doesn't establish that Steam selected the same one.