- Blind mode tutorial
lichess.org
Donate

Engine bug on macOS and iOS?

Since a couple of days ago the engine analysis isn't working on my mac or iPhone, is anyone else seeing this issue?

It just shows an error message:

worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError: Aborted(). Build with -sASSERTIONS for more info

Since a couple of days ago the engine analysis isn't working on my mac or iPhone, is anyone else seeing this issue? It just shows an error message: worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError: Aborted(). Build with -sASSERTIONS for more info

@simonWasHere said in #1:

Since a couple of days ago the engine analysis isn't working on my mac or iPhone, is anyone else seeing this issue?

It just shows an error message:

worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError: Aborted(). Build with -sASSERTIONS for more info

Try the following and give a feedback if it works please.

Before you activate the engine open the settings of the engine.
Set "Threads" to 1. If it works stop the engine set "Threads" to 2.

@simonWasHere said in #1: > Since a couple of days ago the engine analysis isn't working on my mac or iPhone, is anyone else seeing this issue? > > It just shows an error message: > > worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError: Aborted(). Build with -sASSERTIONS for more info Try the following and give a feedback if it works please. Before you activate the engine open the settings of the engine. Set "Threads" to 1. If it works stop the engine set "Threads" to 2.

I’ve tried but the suggestions I’ve seen but I can’t seem to get it to work.

I’ve tried but the suggestions I’ve seen but I can’t seem to get it to work.

@Richard50 said in #3:

I’ve tried but the suggestions I’ve seen but I can’t seem to get it to work.

Whoops, I take that back. What I did was switched engines from that 79 MB one that I usually use to one of the others and then I switched back and it started working again. Maybe it cleared cache or something.

@Richard50 said in #3: > I’ve tried but the suggestions I’ve seen but I can’t seem to get it to work. Whoops, I take that back. What I did was switched engines from that 79 MB one that I usually use to one of the others and then I switched back and it started working again. Maybe it cleared cache or something.

@Richard50 said in #4:

Whoops, I take that back. What I did was switched engines from that 79 MB one that I usually use to one of the others and then I switched back and it started working again. Maybe it cleared cache or something.

Apple has changed the thread handling of the software with the update to IOS 26.2.
Reducing the number of threads is a wordaround. if your method works too, good.

now it works for you?

@Richard50 said in #4: > Whoops, I take that back. What I did was switched engines from that 79 MB one that I usually use to one of the others and then I switched back and it started working again. Maybe it cleared cache or something. Apple has changed the thread handling of the software with the update to IOS 26.2. Reducing the number of threads is a wordaround. if your method works too, good. now it works for you?

Well, I just checked again and actually it doesn’t. I’m using the 79 MB stockfish with the thread set at 2. Two is as low as it goes there is no option for one.

The 7 MB stockfish seems to be working

Well, I just checked again and actually it doesn’t. I’m using the 79 MB stockfish with the thread set at 2. Two is as low as it goes there is no option for one. The 7 MB stockfish seems to be working

No, it still doesn't seem to work with threads set to 2

No, it still doesn't seem to work with threads set to 2

I am seeing really crazy high memory usage (in Chrome on macOS) - I am not sure if it is related to my use of external engines.

I guess it also happens in Safari, which I use on my iPad as a fullscreen web app. Now I can hardly use any built-in engine (currently only the 7 MB version works, with lowest amount of hash) - or it will give that "out of memory" error.

Not sure how to get that working again - killing the app or rebooting does not fix the issue.

I am seeing really crazy high memory usage (in Chrome on macOS) - I am not sure if it is related to my use of external engines. I guess it also happens in Safari, which I use on my iPad as a fullscreen web app. Now I can hardly use any built-in engine (currently only the 7 MB version works, with lowest amount of hash) - or it will give that "out of memory" error. Not sure how to get that working again - killing the app or rebooting does not fix the issue.

@simonWasHere said in #1:

Since a couple of days ago the engine analysis isn't working on my mac or iPhone, is anyone else seeing this issue?

It just shows an error message:

worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError: Aborted(). Build with -sASSERTIONS for more info

Yeah same. Since I updated to iOS 26.2 it’s never worked - well I say never, it sometimes works if I choose stockfish 11 but stockfish 17 always just crashes. Reducing number of threads doesn’t make any difference.

@simonWasHere said in #1: > Since a couple of days ago the engine analysis isn't working on my mac or iPhone, is anyone else seeing this issue? > > It just shows an error message: > > worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError: Aborted(). Build with -sASSERTIONS for more info Yeah same. Since I updated to iOS 26.2 it’s never worked - well I say never, it sometimes works if I choose stockfish 11 but stockfish 17 always just crashes. Reducing number of threads doesn’t make any difference.

I'm also getting this, and on the technology preview as well. It works fine in Vivaldi and Firefox so it seems like a safari issue

I'm also getting this, and on the technology preview as well. It works fine in Vivaldi and Firefox so it seems like a safari issue

This topic has been archived and can no longer be replied to.