5 ms·
I wish the Chrome team would dig into why my Chrome uses nearly all of two cores all of the time with one tab open. The issue (or something similar) comes up al
by aeturnum 6y ago
I wish the Chrome team would dig into why my Chrome uses nearly all of two cores all of the time with one tab open. The issue (or something similar) comes up all the time on their forums and they just lock all the topics[1]. Chrome is such a resource hog under normal operation that it's hard to say when something is going wrong.
[1] https://support.google.com/chrome/thread/17537877?hl=en https://support.google.com/chrome/thread/17537877?hl=en
- username90 6y agoIt doesn't take much cpu for me. Chromes 19 processes combined sits there are 1% cpu and about 1gb ram for me. Probably the sites you are visitings fault. Edit: Looking through that thread seems like some plugins caused the issue.
- aeturnum 6y agoI'm glad their browser works that well for you. It does not for me: https://dl3.pushbulletusercontent.com/dRiiaqbW844ZN3QHGcdWNe7u0xEg7EbY/Screen%20Shot%202021-04-23%20at%204.50.39%20PM.png https://dl3.pushbulletusercontent.com/dRiiaqbW844ZN3QHGcdWNe...
- deleted 6y ago[deleted]
- josephg 6y agoTry disabling all your browser extensions and see if the problem persists. It’s amazing to me how inefficiently a lot of browser extensions are written - eg last I checked, metamask pulls in web3, which is a clown car of javascript that takes hundreds of milliseconds to parse. That code needs to be parsed every time you navigate to a new website. You might not notice a single extension like that, but with a few bad extensions it’s easy for your browser to slow to a crawl. The obvious response is to blame the browser for stuff like this, but it’s usually the extensions that are causing your problems. [1] https://github.com/ChainSafe/web3.js/issues/1178 https://github.com/ChainSafe/web3.js/issues/1178
- aeturnum 6y agoYah, I've tried that. If you read the thread I linked everyone in it (who has not resolved their problem) has tried it. Right now I opened chrome back up and it's sitting at 186% cpu with one tab open and no extensions. screenshot: https://dl3.pushbulletusercontent.com/dRiiaqbW844ZN3QHGcdWNe7u0xEg7EbY/Screen%20Shot%202021-04-23%20at%204.50.39%20PM.png https://dl3.pushbulletusercontent.com/dRiiaqbW844ZN3QHGcdWNe...
- rasz 6y agoopen Chrome task manager (shift-esc), what is loaded in that one tab? does this thing have associated service-worker? heavy on js? webasm? multiple workers running?
- flakiness 6y agoUse Chrome tracing [1] or Perfetto [2] to take a couple of trace when the problem is happening. Then submit a bug with the trace. That's one of the most promising way to report performance bugs. It is especially powerful when you're using Chromebook because Chrome OS integrates Linux ftrace to these app-level tracing and draws a system-wide picture of the workload. (Disclaimer: I used to work on Chrome many years ago.) [1] https://www.chromium.org/developers/how-tos/trace-event-profiling-tool https://www.chromium.org/developers/how-tos/trace-event-prof... [2] https://ui.perfetto.dev/ https://ui.perfetto.dev/
- aeturnum 6y agoThanks! I'll take a look. I've long since abandoned the browser but I like submitting bugs.