So no, it's most likely not as bad as it looks, but that doesn't change the fact since switching to Safari, I almost forgot what my fan sounds like.Īnd then there's this chart. MacOS likely tries to tell Chrome to take it easy, and Chrome likely does take it easy. That's great if you're not running any other macOS apps than Chrome, effectively using Chrome as your operating system, and macOS as a kind of bootloader.īut when you're using Sketch, Final Cut, Photoshop next to Chrome, that seems to be a problem. I'm sure Chrome is going out of its way to manage its memory usage across tabs, keeping the current tab fast and responsive. And you've got to hand it to Chrome: it is fast! It's not a terrible thing that an app actually uses your computer.
The graphs don't tell the full storyīut it's probably not as bad as it looks. Maybe it was the virtual machine blocking Chrome's direct access to my Macbook's* GPU? I decided to run the next test, the one with 54 tabs directly on my own Big Sur installation. Chrome was using way more memory than I thought it would.
0 kommentar(er)
