I have been getting this message: worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError:
Aborted(). Build with -SASSERTIONS for more info. Things to try
• Decrease memory slider in engine settings
• Clear site data for lichess.org
• Select another engine
• Update your browser I am using the memory minimum. Has anyone else seen this ?
I have been getting this message: worker sent an error! https://lichess.org/assets/hashed/sf171-7.601fb0e9.js:13: RuntimeError:
Aborted(). Build with -SASSERTIONS for more info. Things to try
• Decrease memory slider in engine settings
• Clear site data for lichess.org
• Select another engine
• Update your browser I am using the memory minimum. Has anyone else seen this ?
I've been getting the same error since yesterday, using the latest version of Safari (26.2). Altering engine settings, clearing my site data and restarting my computer has made no difference.
I've been getting the same error since yesterday, using the latest version of Safari (26.2). Altering engine settings, clearing my site data and restarting my computer has made no difference.
I have the same issue. Switching between the engines temporarily solves this, but I'm looking for a permanent solution.
I have the same issue. Switching between the engines temporarily solves this, but I'm looking for a permanent solution.
Yes, Futurefeels, same here. happened when I upgraded to macOS Tahoe 26.2.
Yes, Futurefeels, same here. happened when I upgraded to macOS Tahoe 26.2.
This is a Safari bug https://github.com/lichess-org/lila/issues/18894
if this is a safari bug, is it something that only Apple can fix? has anyone reported this to Apple?
if this is a safari bug, is it something that only Apple can fix? has anyone reported this to Apple?
@qbpvd said in #6:
if this is a safari bug, is it something that only Apple can fix? has anyone reported this to Apple?
The problem is fixed in WebKit, but Apple needs to update Safari with the updated WebKit.
@qbpvd said in #6:
> if this is a safari bug, is it something that only Apple can fix? has anyone reported this to Apple?
The problem is fixed in WebKit, but Apple needs to update Safari with the updated WebKit.
Ah, ok, Thanks for letting us know!!
Ah, ok, Thanks for letting us know!!