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

100% cpu #1

Open
MadameMinty opened this issue Jan 25, 2017 · 5 comments
Open

100% cpu #1

MadameMinty opened this issue Jan 25, 2017 · 5 comments

Comments

@MadameMinty
Copy link

MadameMinty commented Jan 25, 2017

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.

@dinoboy197
Copy link
Member

Thanks for the report. I have a couple of questions to help me narrow down what might be going on:

  • Are you certain that PageAccel is causing your CPU spikes? (Just want to be completely sure that we're chasing the right cause)
  • Which version of PageAccel do you have installed currently? (You should be able to find this in the Chrome Extension panel.)
  • Are there particular pages or websites on which PageAccel is spiking to 100%, or is every page?
    • Would you provide one particular page on which the CPU goes from low usage to high usage?

@MadameMinty
Copy link
Author

  • Chrome Task Manager showed it's this extension specifically.
  • It's version 1.7.4, one updated 10 days ago. I noticed this issue over the last week but only today realized it's not just Chrome but an extension.
  • Really inconsistent. Right now I don't do anything and the extension unloaded itself. I opened the same exact pages when I detected the spike, and it just checked them for amp versions and relaxed itself. It seems independent of the website.

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?

@dinoboy197
Copy link
Member

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!

@MadameMinty
Copy link
Author

It just happened on 1.7.6.

Extension and tab list: http://i.imgur.com/x8Xxx65.png
Red rectangle: the window that miiight be a culprit. I'm actually guessing the extension might break on Google Image Search. Not sure. Disabled and enabled to restore normal function, then refreshed GIS to no effect.

@dinoboy197
Copy link
Member

dinoboy197 commented Jan 27, 2017

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:

  • Restart Chrome (or wait until the PageAccel extension updates itself to 1.7.7).
  • Go to the Extensions page (chrome://extensions), and make sure the page is in Developer mode (there is a checkbox at the top right of the page).
  • Find PageAccel, look for "Inspect Views", and click on the "background page" link. A window will open (likely it has a title starting with "Developer Tools").
  • Click the "Console" tab in this new window and leave it open in the background or off to the side.

Then, the next time you notice that PageAccel is taking up more CPU than you'd like:

  • Go to the newly opened window.
  • The Console tab should have lots of rows being printed in it.
  • Wait until you've got about 10 or 20 seconds of rows, then copy and paste the last 10 or 20 seconds of rows here (or into a GitHub Gist, or any other text file that you can attach to this issue so that I can take a look).

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.

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

2 participants