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

EZBlocker CPU usage after boot when Spotify is not yet used #256

Open
miku84 opened this issue Apr 5, 2021 · 2 comments
Open

EZBlocker CPU usage after boot when Spotify is not yet used #256

miku84 opened this issue Apr 5, 2021 · 2 comments

Comments

@miku84
Copy link

miku84 commented Apr 5, 2021

Hi,
I noticed tha following:

When Spotify is enabled on boot and EZBlocker starts with it and Spotify is not yet used after the current boot, then EZBlocker eats CPU 3-4% constantly. I tried it in multiple PC, happens the same.

But after Spotify starts (even 1 sec is play enogh), then EZBblocker CPU usage disappears to normal level (~0,2%).

I think after startup EZBlocker may stuck somehow after boot when Spotify is not used or want to block Spotify very badly, that is why it tries to do something (3-4% CPU), but there is no play in Spotify at all, so it seems unnecessary that EZBlocker eats CPU for nothing.

I hope it can be fixed.
Thanks

@IO2I
Copy link

IO2I commented Jun 20, 2021

I have the same issue but instead of 4% usage, it's like 20%.

@Astrosp
Copy link

Astrosp commented May 13, 2022

In EZBlocker Window there is a option for Start EZBlocker on Startup
uncheck that and restart

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants