Crash about stockfish HOT 12 CLOSED

I fully agree that it is completely ludicrous. Crashing is never acceptable, no matter the complaints about how difficult error validation may or may not be, or how crappy UCI is. Crashing is simply rude, and worse, potentially abusable. (Admittedly a chess engine isn't high on the list of attack vectors, but it's the principle of the thing.)

Crashing is not acceptable behavior, bar none, no ifs ands or buts. And yet here we are...

from stockfish.

Since this wasn't posted yet, this is the repo of the mac app: https://github.com/daylen/stockfish-mac

from stockfish.

Also tried with "recommended settings" of:
Threads: 4
Hash MB: 4096
Skill level: 20

Behavior is unchanged.

from stockfish.

https://github.com/official-stockfish/Stockfish/wiki/Stockfish-FAQ#stockfish-crashed

from stockfish.

NNUE cannot handle more than 32 pieces at all. Turn it off and it will probably work (although IIRC there are some illegal positions that will still crash)

from stockfish.

Putting aside how ludicrous this all is...

What is this supposed to mean?!

also:
A) you opened an issue about a third party app, not our problem…
B) see the link posted above

from stockfish.

What is this supposed to mean?!

It means that it's not a standard position.

A) you opened an issue about a third party app, not our problem…

Isn't Stockfish your app? It is listed here: https://stockfishchess.org/download/ -> https://apps.apple.com/us/app/stockfish-chess/id801463932

B) see the link posted above

Gonna take a look now

from stockfish.

NNUE cannot handle more than 32 pieces at all. Turn it off and it will probably work (although IIRC there are some illegal positions that will still crash)

Ah, so basically it crashes because it's a "Fairy" position, and not reachable in standard chess? That makes sense. Thank you!

from stockfish.

No the stockfish app in the App Store is developed by an individual person

from stockfish.

No the stockfish app in the App Store is developed by an individual person

Ah, thanks!

from stockfish.

I fully agree that it is completely ludicrous. Crashing is never acceptable, no matter the complaints about how difficult error validation may or may not be, or how crappy UCI is. Crashing is simply rude, and worse, potentially abusable. (Admittedly a chess engine isn't high on the list of attack vectors, but it's the principle of the thing.)

Crashing is not acceptable behavior, bar none, no ifs ands or buts. And yet here we are...

Ohhhhhh, now I get what happened. @Disservin

My original comment might be interpreted to say "crashing is ludicrous".

No! That is not at all what I meant.

What I did mean is: putting aside how ludicrous it is of someone to want to analyze such a position.

Ah, misunderstandings... Don't we all love when they happen...

from stockfish.

Oh. lol. well, i still find stockfish crashing on malformed input to be ridiculous, but apparently that isn't what this issue is about at all. and also yes i'm willing to agree that your OP position is also a bit ludicrous 😆

from stockfish.