Banksia GUI released

[phhnguyen]

Posting a follow-up to my own earlier post where I reported Banksia GUI would randomly exit and crash, sometimes leaving engine tasks running and sometimes not. Through trial and error, I have found that the one setting that would prevent the crashes for me is to deselect the "Game to database" option in the Tournament Logs dialog box. I have now let it play > 2,000 games over 4 tournaments with many engines and not a single crash since this change.

For background, I was on Windows 10 Pro and now Windows 11 Pro.

Thanks for the very useful software.

Great find. Thanks for that!

FYI: BSG is abandoning its own database format. Instead, it is going to support Open Chess Game Database Standard (a kind of SQL format).

[phhnguyen]

Good morning Pham,
what are these engines with weird names like for example: jane:Stockfish14, jane:Minic10, in your picture.

jane:Stockfish14 means Stockfish, version 14, running from another local computer named "jane".

[phhnguyen]

Hmm, I wonder if 0.53 was the end of the road. The developer was very active before, but not a peep since the release (he's in other threads, though).

Don’t worry, I have been around doing something different, just to refresh my brain. It is not good to stick to a thing all the time and for such a long time! I am still active but not that active as before, just to keep some time to think, try other tasks, enjoy other things as well as life

I am also very happy to see many people can help, support other people on BSG’s issues. Thanks all!

BTW, the different thing I have been working on actually relates to BSG: a new database format standard (Open Chess Game Database Standard) that will be supported by BSG from the next release.

[phhnguyen]

I have regular crashes with Banksia, both running on macOS and on Linux. I tracked the issue down to the parsing of engine output. read_stdout->parseLine->parseInfo->vector out of range.

During this crash, Banksia quits and leaves the engines running. kill -9 required.

I believe this is the same crash I had with earlier versions and that I fixed by not outputting UTF-8 strings ... But this time, crash occurs with UTF-8 and ASCII.

Thank for the bug report. The info is quite good for me. If you could, give me a bit more: which engines are involved, the timers.

[AlexChess]

I have regular crashes with Banksia, both running on macOS and on Linux. I tracked the issue down to the parsing of engine output. read_stdout->parseLine->parseInfo->vector out of range.

During this crash, Banksia quits and leaves the engines running. kill -9 required.

I believe this is the same crash I had with earlier versions and that I fixed by not outputting UTF-8 strings ... But this time, crash occurs with UTF-8 and ASCII.

Thank for the bug report. The info is quite good for me. If you could, give me a bit more: which engines are involved, the timers.

Very happy that you are back, Pham!!!

[Ozymandias]

Hmm, I wonder if 0.53 was the end of the road. The developer was very active before, but not a peep since the release (he's in other threads, though).

Don’t worry, I have been around doing something different, just to refresh my brain. It is not good to stick to a thing all the time and for such a long time! I am still active but not that active as before, just to keep some time to think, try other tasks, enjoy other things as well as life

I am also very happy to see many people can help, support other people on BSG’s issues. Thanks all!

BTW, the different thing I have been working on actually relates to BSG: a new database format standard (Open Chess Game Database Standard) that will be supported by BSG from the next release.

Quite understandable. May I infer that there won't be any move variations in the next release?

[Wilhelm]

Pham, you'r alive

cheers

[phhnguyen]

Thanks all! I feel warm in my heart

As usual, I have noted down all comments, reports, suggestions and will work with them.

[AlexChess]

+1 dear Pham!

[ydebilloez]

I have regular crashes with Banksia, both running on macOS and on Linux. I tracked the issue down to the parsing of engine output. read_stdout->parseLine->parseInfo->vector out of range.

During this crash, Banksia quits and leaves the engines running. kill -9 required.

I believe this is the same crash I had with earlier versions and that I fixed by not outputting UTF-8 strings ... But this time, crash occurs with UTF-8 and ASCII.

Thank for the bug report. The info is quite good for me. If you could, give me a bit more: which engines are involved, the timers.

It is related with Belofte (versions before 2.1.5). I output some debug information info [depth] [pv] stringin the info string part during other output (score/pv/currmove/...). The good news is that if I omit this output, no crashes anymore. In the next version of Belofte, I will remove the extra output if debugging is disabled.

As a sideline, the

Code: Select all

info [depth] [pv] string

output adds up in the top line under engine info. On mac, this is done in a small font, so not disturbing. On Linux however, the font is much bigger than the following lines with the search output and this is not pretty.