![]() The Google Chrome browser is an often-cited culprit as a processor "hog." More specifically, the Google Chrome Helper (Renderer) often consumes a disproportionate amount of processor resources. I exchanged emails with an Apple spokesperson about the issues. The problem will typically show up quickly but sometimes it won't manifest itself until after extended use. If I had more than a dozen tabs open and needed to frequently switch between tabs, my workflow slowed down enough to make me wish I had another laptop handy. In some cases when the load was heavier than usual, the system slowed to a crawl and tabs sometimes became unresponsive. ![]() ![]() That included streaming cable TV news and other cable shows (one at a time) in the background. ![]() Because I was relying on one system (not the several systems that I typically use simultaneously) I had more tabs open in Safari and Chrome. How I used the MBA changed on the road trip. That's when lots of multi-tasking came pretty close to bringing the system to its knees in some cases. The performance problems didn't begin to become chronic* until the summer when I went on a long road trip with the MBA.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |