MacOS26 has wrecked my M1 MacBook Pro

[alexjholland]

Since updating to MacOS26 my system resources are eaten alive by Chrome and Figma.

I believe this might be the Electron bug?

Every 1-2 days I have to restart, or wake up and find my Macbook has restarted itself.

Every Apple device that I own is worse due to these insane, dreadful updates.

It's almost as if Apple are crying out for help and trying to prove they have dropped the ball.

 

[p33t3r]

Well, if the resources are, as you say, eaten alive by Chrome and Figma, and none of these are Apple's applications I fail to see how Apple can be at fault here. These are obviously subpar applications with glaring memory handling problems.
Or do you run any Chrome extensions that can be the culprit? I don't know anything about Figma.

 

[Fishrrman]

Chrome?
Use something else.
ANYTHING else...

 

[nmt1900]

If you think this is Electron bug then try to remove Electron-based apps and see if that helps.
P. S. It looks like main page of Figma's website can eat into resources easily if left open for a long time. Welcome to "brave new world" of animated web page designs...

 

[PotentPeas]

Well, if the resources are, as you say, eaten alive by Chrome and Figma, and none of these are Apple's applications I fail to see how Apple can be at fault here.

If it was working fine before the upgrade, and it is broken after the upgrade, how can you do anything but blame the upgrade ...?

A world where Apple says "everyone who uses [this class of application] must upgrade their apps before they work on our new OS" ... I mean, that makes sense in the case where CPU architecture changes are happening (i.e. dropping 32-bit support), or for maybe system/security-focused apps that need to hook into the OS at a low level ... but for basic productivity apps, this is a failure in maintaining basic backwards compatibility from one OS to the next. It's not like these are obscure apps that Apple couldn't have checked.

Even if the apps are "at fault" for doing something weird that causes this behavior. The fact that it was working fine for so long means that this is a regression caused by Apple.

 

[fisherking]

If it was working fine before the upgrade, and it is broken after the upgrade, how can you do anything but blame the upgrade ...?

A world where Apple says "everyone who uses [this class of application] must upgrade their apps before they work on our new OS" ... I mean, that makes sense in the case where CPU architecture changes are happening (i.e. dropping 32-bit support), or for maybe system/security-focused apps that need to hook into the OS at a low level ... but for basic productivity apps, this is a failure in maintaining basic backwards compatibility from one OS to the next. It's not like these are obscure apps that Apple couldn't have checked.

Even if the apps are "at fault" for doing something weird that causes this behavior. The fact that it was working fine for so long means that this is a regression caused by Apple.

if it's an apple app, apple is at fault, of course. if it's a third-party app, it's up to that developer to keep up with OS changes, the most important reason we get betas....

 

[chrfr]

Even if the apps are "at fault" for doing something weird that causes this behavior. The fact that it was working fine for so long means that this is a regression caused by Apple.

The bug in Electron apps is due to Electron using an undocumented private Apple API it shouldn't have been using. Many major apps have now been patched but a bunch have not.

Shamelectron - Electron Apps macOS Tahoe GPU Performance Tracker

Track which Electron apps have fixed the major GPU performance issue on macOS Tahoe. Real-time status monitoring of Electron app compatibility with macOS 26.

avarayr.github.io