-
Notifications
You must be signed in to change notification settings - Fork 17
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
High CPU usage due to progressbar #36
Comments
sounds like #32 |
able to replicate high cpu usage after pulling down the repo and debugging. |
How do you replicate the problem? I have not yet been able to replicate it. |
I was able to recreate it by just pulling it down and running it in debug. |
Interesting. I use a AMD Ryzen CPU. Maybe this problem only happens with a Intel CPU. I will try to test it with a Intel CPU. |
Can now also recreate the problem: If you use Marquee and then switching to block or continuous it cause high cpu usage. If you never touch this option, there is no high cpu change. |
It appears both block & continuous cause high cpu usage. (higher than chromakey vcam...)
Marquee is the least impactful.
An option to disable progress bar completely would be nice.
The text was updated successfully, but these errors were encountered: