It gives a pop up that says "Your external engine does not appear to be connected. Please check the network and restart your provider if possible."
Googling is not helpful.
I don't know how to fix / reset. Any help would be appreciated.
Can you please try clearing your cookies and site data for lichess and trying again? If you are on firefox click the pad-lock and on chrome, click the toggle icon. The icon would be immediately to the left of your address bar.
Thank you for the suggestion. I'm on Chrome. I deleted ALL cookies and caches for all of chrome, and the problem still persists. It happens with all selections, although my main one is the Stockfish 16 40MB. Sometimes the engine will work for a move or two even after the popup but then just hangs forever afterwards. Happens both logged in or out.
My OS is 32-bit, would that matter?
I’m on mobile right now so I can’t provide too much insight into how it behaves, but wanted to drop some thoughts (mainly so I’ll remember to check again later).
I’d need to see the browser profiler to confirm, but it is possible that the configuration between the threads and memory may be hitting the 32bit cap in the browser.
Also: dropping a pin in my brain to look at more granular settings/details for the engines and what knob turns which lever so to speak.
EDIT: Forgot to add steps to try:
Scenario 1:
* Lower threads to minimum
* Lower CPU to minimum
* Disable NNUE (if enabled already)
* Disable Infinite analysis (if enabled already)
Scenario 2:
* Lower threads to minimum
* Set CPU as high as allowable by setting
* Disable NNUE (if enabled already)
* Disable Infinite analysis (if enabled already)
Scenario 3:
* Increase threads to maximum
* Set CPU to minimum
* Disable NNUE (if enabled already)
* Disable Infinite analysis (if enabled already)
If you can try those three configurations and share the outcome it would be greatly appreciated!
Testing with Stockfish 16 NNUE (I do not see a way to turn off NNUE independently in the new menu), 40 MB
Scenario 1:
8 second search
1 line
2 threads
16 MB memory
Result: Works fine
Scenario 2:
8 second search
5 lines
32 threads
16 MB memory
Result: Sluggish but working, no errors.
Scenario 3:
8 second search
5 lines
32 threads
512 MB memory
Result: Immediately throws error as above.
Scenario 4:
infinite second search
5 lines
32 threads
16 MB memory
Result: Sluggish but working, no errors.
Still in Scenario 4,
upping memory to 32 MB and waiting 10 seconds: Sluggish but working, no errors.
upping memory to 64 MB and waiting 10 seconds: Sluggish but working, no errors.
upping memory to 128 MB and waiting 10 seconds: A bit less sluggish, working, no errors.
upping memory to 256 MB and waiting 10 seconds: Immediately throws error as above.
Hardware:
Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz 3.40 GHz
Installed RAM: 16.0 GB (3.46 GB usable)
Software:
System: 32-bit operating system, x64-based processor, Windows 10 Home 22H2 build 19045.3930
Browser: 120.0.6099.225 (Official Build) (32-bit) (cohort: Stable)
Thank you very much for the recommendations. At the very least it helped me find what settings I can use consistently; I don't know enough CS/programming to know if the results make a lot of sense or expected behavior, but anything else I can do to help I'm happy to do.
Doing some rough/simple calculations I’m fairly confident you are hitting the maximum memory “available” due to 32-bit capping at around 4GB.
This should be the theoretical limit you are telling the engine it can use: 32 threads * 256MB per thread = 8196MB thus exceeding what is actually available and causing what would be considered an Out Of Memory error.
You somewhat proved this theory by being able to run 32-threads at 128MB per thread= 4096MB; the engine likely won’t hit this but it passes the checks of “what can I use”.
If you look at the specs you posted one of the lines says “Installed Memory: 16GB (3.46 Usable)” thats telling you that there is 16GB of RAM physically present in your machine, but the OS can only use 3.46GB.
Your hardware and processor listed running x64 so running 64-Bit shouldn’t be a problem if you’ve got the time/means to migrate it over.
64-bit is very much the standard now and it’s hard to find much running 32-bit these days, so the browser analysis tool likely doesn’t account for the possibility of running over the cap.
Any reason you are running 32-bit? Looks like you have plenty of RAM that can’t be utilized under 32-bit and I’d be happy to help you migrate over to 64-bit if you’d like (feel free to DM me).
@Valis2501There's a bug in that dialog recently introduced. Right now it blames "external engine" anytime anything goes wrong. :)
The dialog bug is already fixed and should provide more info once deployed. It's likely you've an allocation error. And you should also reduce your threads to match the number of cores in your CPU (the green tick mark). You stockfish will perform better.
Most importantly, it is vanishingly rare that a difference relevant to humans exists between 16MB and 512MB hash sizes on timescales of 20s or less. Adjust your Memory slider until your machine doesn't break. Then use that one.
I probably know the solution, You need a Programm called FixWin10
so use these 3 options there, if they are there, and reset PC
Also check Yourself for viruses somehow, they could harm your internet connection even if you was infected and clean them all
@foxtracks Thank you, this makes sense now.
@schlawg Thank you for the information about the hash sizes! Appreciate it.
