obsproject / obsproject/obs-studio

CPU usage in Stats tab inaccurate and consistently underreported.

Open
#6,525 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

27.2.4

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/5VFgNqpO5YlrB3eQ

OBS Studio Crash Log URL

No response

Expected Behavior

CPU usage reported in OBS Stats panel and bottom right corner appears to be consistently underreported.

Here is a screenshot capturing both Task Manager and OBS at the same point in time.
image
image

__

Current Behavior

CPU usage is consistently under reported.

Steps to Reproduce
  1. Start OBS with usual sources.
  2. Measure CPU usage from both OBS stats and Task Manager
  3. Compare results.
    ...
Anything else we should know?

Windows 11 21H2 22000.675
Ryzen 5600x
16 gig of ram
Geforce RTX 3700

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing on Windows 11 with the listed Ryzen 5600X setup, comparing the Stats panel and bottom-right CPU value with Task Manager while following the issue's steps. Review the OBS log URL for runtime context and trace the existing CPU-reporting path; done means OBS no longer consistently underreports CPU usage against Task Manager.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.