cpugooglegoogle-chrome
I'm trying to figure out what the devil is wrong with Chrome getting 100% cpu once in a while. I sampled the process Google Renderer. Not sure where to go from here. any advice?
process sample: https://gist.github.com/hadifarnoud/2371a33a5c3f39ede034
You can put either of these in an Automator service using a applescript Action.
Then set a keyboard shortcut with the Services in keyboard system preferences's Keyboard Shortcuts.
Note the 'Service receives' settings in the screen shots. This will make sure the Menu appears in all app's services. (The other apps may need to quit and re open before they pick up the short cut)
Chrome.
tell application "Google Chrome"
reload active tab of (get window 1)
end tell
Safari.
tell application "Safari"
tell document 1 to do JavaScript "javascript:location.reload(true)"
end tell
Services.
Service Menu -In iTunes
By observing log messages in ~/Library/Logs/Ubiquity/<my username>/, I realized that Ubiquity (iCloud process) kept trying to create a file in a folder that doesn't exist:
I opened up the Terminal and created this directory and its parent directories up to .ubd:
cd ~/Library/Mobile\ Documents/
sudo mkdir .ubd && cd .ubd
sudo mkdir peer-E2B13E4F-56F7-C79B-1621-E30738B638FE-v23 && cd peer-E2B13E4F-56F7-C79B-1621-E30738B638FE-v23
sudo mkdir ftr
Then I changed the newly created directories' owner from root to myself:
cd ../..
sudo chown -R <my username> .ubd/
The fan turned silent instantly.
Best Answer
You can view Chrome's page memory usage by pressing the button in the top right of the Window. There you will get this menu:
When you click 'View Background Pages' you'll see a window like this:
This obviously narrows down page and extension usage by memory and CPU. This should help finding out exactly what's going on with it.
The 'Stats for nerds' link sends you to
chrome://memory-redirect/which breaks down their memory usage even more.Side note when I notice chrome using a lot of memory and open
/Applications/Utilities/Activity Monitor.appI typically see it is caused byPepperFlashPlayer (Chrome Plug-In Host)which is Chrome's built in Flash player. It is known for hogging CPU