Chess analyze results in Foutcode: SBOX_FATAL_MEMORY_EXCEEDED

Whenever I Analyze a game chrome crashes and throws a : SBOX_FATAL_MEMORY_EXCEEDED error. This is really annoying since I can't really analyze anything properly. 

It starts crashing the moment I make a move that wasn't played in the game itself. 

I am runnig chrome: Versie 97.0.4692.71 (Officiële build) (64-bits)

Same for me

Are you on that same Chrome version? If so you should upgrade to a newer one.

I was on version 109.0.5414.74. Now on 109.0.5414.75 but I highly doubt this will solve the issue. I'll report back if I have more info.

for me it just started happening today and it always happens when i win or lose a game, very annoying

So, is it only after games? Do you have Automatic Analysis on?

Has been happening to me too. No automatic analysis

I've solved mine.  There was a Legacy Microsoft Power Automate extension that once I remove it.  The error went away.

For those with the crash, do you have Stockfish 15 NNUE on in analysis settings? If so, try switching that to Stockfish 15 (faster) and see if you're still getting crashes.

Same here

Just to add, I've tested with both versions of Stockfish configured.

For me, on Windows, Stockfish 15 NNUE will consistently crash while spectating but Stockfish 15 (faster) doesn't.

Both crash on game end when playing, though it's not after every game. Didn't see issues with Komodo and turning the option off while not actively analyzing should prevent crashing, until the site can figure out the root cause.

As far as I'm aware, the problem is with Chrome 109 and Chromium based browsers that share that code (though I haven't tested those). That version came out January 10th, around the times reports of crashing started happening, and I haven't heard of any recent Stockfish related code changes that had been made by the site.

 Attempted this on Edge (chromium). error still occurs

Yeah, as mentioned in my last post, it's some change on version 109 conflicting with Stockfish (and maybe only on Windows). It doesn't seem to impact Komodo and may not have issues in incognito mode.

The site should have a mitigation in place soon until a full solution is found.