-
Notifications
You must be signed in to change notification settings - Fork 74
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 when running in background #210
Comments
@Mizzick any idea how we can troubleshoot this? Obviously, we cannot reproduce this so I guess the only way would be to start writing a log file & introduce logging level |
We actually do write the log file. |
This problem exists on multiple macOS devices including Macbook Pro and Mac mini, so it should be reproducible on your side. |
@interpretor could you please try the standalone build just in case? |
Same issue here (cpu usage in background when not fetching/checking updates). I did a bit of digging with dtruss ( Viewing/extracting with npm Some sample dtruss output (repeats over and over and over): expand for output
|
Also, no adguard logs in |
FWIW the beta from 3 days before doesn't show this behavior. |
Well, this must have something to do with the sandbox that is used in the Mac App Store build. Standalone build is different. |
OK, but what do I have to do to get the final release from github running? It crashes upon opening and says: |
I also would be interested in an answer to this question. The final release crashes upon startup. |
@amok-san @interpretor the release is fixed, thanks for your attention |
Hi, |
Hi, |
We don't understand yet why there is such a difference between the AppStore and the standalone build. Once v1.5 is released on AppStore, we'll revisit this issue. Hopefully, it'll happen next week. |
Hi everyone, we've just released v1.5 to MAS: https://github.com/AdguardTeam/AdGuardForSafari/releases/tag/v1.5.4 Could you please check if the issue is still present? |
It's fixed for me! Well done, guys |
Awesome, thanks for testing it! |
While the release is great (added up to 300.000 possible filters), I unfortunately have to tell you, that the problem still exists in the current App Store version of your application. Having about 5-6% CPU usage while doing nothing. |
:( |
@interpretor I wonder what's the difference between yours and @cpgn configurations. What MacOS versions do you have? |
Ignore my previous post. It seems fixed now! |
🎉🎉🎉 @interpretor thank you:) |
Fixed here also! ❤️ |
Steps to reproduce
Expected behavior
Adguard for Safari should not have any noticeable CPU usage when running in background
Actual behavior
Adguard for Safari uses about 3 - 5% on a Quad-Core i7
Your environment
The text was updated successfully, but these errors were encountered: