Critical bug - Web version - since today

If the browser itself crashes, that is being caused by some code on the client side that the browser can't handle.  In those instances, knowing the exact error the browser is showing is important to help track down what it might be.

If it's a 5xx error, that is something else, and recently has been causied by very high server loads. 

The two are separate events and causes.

Aw Snap!  Something went wrong when displaying this page
Error Code: SBOX_FATAL_MEMORY_EXCEEDED

As mentioned, staff have tickets in on that. I know one staff member had it happeen,  but it's not clear what caused it as far as I'm aware.

For those with the issue, what engine do you have configured for analysis and how many lines?

Look, Martin. This has nothing to do with the configuration of engine for Analysis with the number of lines. The fact is, chess.com needs to get this sorted out. as whatever the issue may be, is coming from something broken on their end.

This crash happens at any given point during a game or while spectating a game. whether the engine is on or off.

I'm trying to gather additional information to try all the conditions it might happen on (recreating the conditions for the bug). It's good to know that you also get the issue when spectating.

The issue is an interaction with the browser and the client code (very unlikely it's related to the server, though it could happen when pulling data from the server and ultimately that would be client code bug to fix). Again, every bit of information helps staff to help pinpoint where the issue could be.

Martin, the problem just got worse for me. I again encountered the same Fatal error, except this time, no matter how much I try to connect back to Live Chess, I keep getting the error "You have been disconnected, please refresh the page to connect"

The funny thing is, I tried using another account just to test if the problem was really with Live Chess, and surprisingly Live Chess worked with this account. My this account isn't able to establish a connection with Live Chess anymore after receiving a Fatal Error in-between a game. What the hell is going on?

I am having this same issue and clearing the cache does not fix it for me.

Seems to happen when I lose more so than when I win.  So it happens a lot. :-)

Does not happen in Edge or Brave Browsers

I had that come up once when testing. A refresh got it working.

For those experiencing the issue, do you have Stockfish 15 NNUE configured? If so, try switching to regular Stockfish and see if that stops the crashing.

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.

I'm having the same problem...just started yesterday. After every game im booted off the site and get this message.

SBOX_FATAL_MEMORY_EXCEEDED

I reported it , cleared cached, restarted etc.

Any ideas?

For me the error disappeared after a few days. Guess it was solved and your bug is a new one. Maybe put "Live chess > automatical analysis" off.

Which browser and what engine is configured for you?

Chrome browser.... Not sure which engine... I turned off automatic analysis and it no longer happens but i'd like to get that back

found the engine ...looks like stockfish 11

Hmm. Thanks for the information.

Those with the issue, a recent change was made, is it still happening?

Hi Martin... It seems to be working just fine now. Thank you for looking into it.