-
Notifications
You must be signed in to change notification settings - Fork 0
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
100% cpu #1
Comments
Thanks for the report. I have a couple of questions to help me narrow down what might be going on:
|
I'll try to note specifics when it happens again. Also I tested some other extensions but I don't think it's a conflict. I could provide their list I suppose? |
Sure, any extra particulars about reproducibility would help. Obviously, I'm not counting on you to do QA for the project, but of course, if you come across anything suspicious, please do let me know. If it's easy and quick for you to get a list of the other extensions that you have, I'll install those over here and see if I can reproduce. In the mean time, I'm going to look into some good ways to attempt to pinpoint the cause. I've actually released an update (1.7.6) just tonight for a different issue; I don't think it will affect your 100% cpu usage, but if you do see a difference, please let me know. Thanks again; hoping to get to the bottom of this soon! |
It just happened on 1.7.6. Extension and tab list: http://i.imgur.com/x8Xxx65.png |
Thanks for that screenshot. Myself and other testers over here haven't been able to reproduce the high CPU yet, so here's what I'd like to try next. I've pushed an update which includes timestamps and tab information on debug logs (1.7.7), which should allow PageAccel to dump out a bunch of diagnostic information for me to look at. Would you be able to do the following:
Then, the next time you notice that PageAccel is taking up more CPU than you'd like:
Hopefully, this debugging output will allow me to spot something that is amiss, and I'll be able to correct it. You're our first "remote debug" for PageAccel so thanks for your continued patience. |
After the last update the extension sometimes seems to go haywire and tries to take 100% time of one CPU core (shows as 25% in Chrome Task Manager on my quad core). Chrome 55.0.2883.87 m on Windows 10 x64.
In fact even if not it constantly oscillates between 5-10% for no reason.
The text was updated successfully, but these errors were encountered: