![]() In which case, I guess you might have to stick with Brave, Edge, Firefox, etc. You might not want to run a browser without Grammarly, too. But those sites are rare for me, despite living online all day every day. I know Safari isn’t for everyone or every site-I used a site the other day that wanted to use my camera and microphone and audio refused to work. Safari runs fast and with a solid ad blocker like 1Blocker or AdGuard installed, it’s efficient and I have no problems with WordPress’ Gutenberg editor or any other site I visit. Once I uninstalled Grammarly these problems evaporated. The result is a huge outlay in memory consumption, processing, and ultimately battery drain. This layout would be confusing since none of it is a complete sentence and the text appears disjointed from each subsequent block of text. In the graph image above, for instance, Grammarly would want to read all the dates, percentages, and button labels. The problem is this dramatically balloons the amount of text Grammarly has to parse. This text OCR service does not run in other browsers. But it was being rendered as text and I suspect Grammarly wanted to “read” it like it does all other text. It’s a handy way of copying text from a photo or getting a quick translation of a word. The system-wide function that works in Mail, Notes, Preview, and your iPhone camera is also in Safari and it reads the text of images. I’m not sure, but I think the problem might be with Safari’s new text OCR features that shipped in macOS Monterey. So what’s going on with the Grammarly plugin in Safari and its high resource usage? This also accounts for reboots, quitting apps, and using different browsers across this period. IStat memory pressure chart over the last 30 days, with significant drops in pressure after uninstalling Grammarly. The drop in memory pressure was noticeable after just one day, but here’s the graph after a few: I uninstalled Grammarly entirely from my Mac by removing both the plugin and the Mac app (which is really just a crummy electron web wrapper). Grammarly was the constant in all of them. plus, in Safari I ran 1Blocker, in Brave and other Chromium browsers I used uBlock. I narrowed the cause to Grammarly, which was the only constant between browsers and would often spike for a second or two in Activity Monitor’s processes usage. So I started tracking usage in Activity Monitor and memory pressure with iStat Menu. And I had the most noticeable problems on my Mac, but could sorta replicate this WordPress page/post editor performance in Safari on my iPad, which also had Grammarly installed. The only solution was to quit and re-open the browser, which is annoying since you get logged out of a lot of stuff.īrave didn’t have this, but still consumed more battery than Safari. Moving Gutenberg blocks and inserting or removing blocks in a WordPress site, something I do a lot, would, after a while, slow to a visible crawl in Safari. I got suspicious when I realized Brave and other Chromium browsers didn’t struggle with WordPress’ admin dashboard. The Grammarly plugin, which I had installed on all my browsers, was doing something to my MacBook Pro. I took it on gospel, then went to go try Brave, Firefox, and others for a while and came away thinking, “Something must be wrong with Safari.” But that was not what I found in months-years even-of use. And Safari on macOS certainly wins the award for most efficient in memory and battery usage. I, like so many others, am always trying to find “the best” browser. ![]() ![]() I’m posting this here for anyone that might be Googling around for some causes or solutions to problems using Safari on macOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |