search

kobanium / aobazero

Aoba Zero
Other
54 stars 8 forks source link

Program crashed #8

Open sbbdms opened 5 years ago

sbbdms commented 5 years ago

About an hour ago I started "click_me.bat" and left for a shower. When I came back, I saw that the program has crashed... However, it seems that the current program doesn't have a function that can record the crash information and save it as a log, so it might be hard to find out why it crashed... The screenshot below is the only information I can get from the crash. The number of weight it used before crashing is 558. Did the program crash because of the conflict of multithread? Or did it crash because of this specific game position? Crashed

yssaya commented 5 years ago

Thank you for bug report. It seems aobaz.exe crashed, and autousi.exe was ok. Log is stored in log/engine000.log. But it is only usi command, and no information of error message.

I made your position and tried 10 times on my 2080 Ti with ubuntu 16.0.4. But I could not find any trouble. I'll test on my Windows 10.

$ bin/aobaz -p 800 -n -m 30 -w ~/test/extract/w000000000558.txt

position startpos moves 2g2f 3c3d 2f2e 2b3c 3i3h 4a3b 7g7f 4c4d 4g4f 3a4b 3h4g 4b4c 4i5h 8b4b 4g5f 5a6b 7i7h 6b7b 8g8f 4c5d 5i6h 4d4e 8h3c+ 2a3c 4f4e 5d4e 2e2d 2c2d 5f4e 4b4e P4g B8h B7g 8h7g+ 8i7g B8h B*2a 3b4b 2h2d 8h9i+ 2d2b+ go visit

sbbdms commented 5 years ago

This is the log file. (I haven't closed the program yet) engine000.log

yssaya commented 5 years ago

Thank you for your log file. Log file position is same as I made. And there was no error info. I think I can not get more information. Please close program.

sbbdms commented 5 years ago

Thanks... However I think it is still a potential issue so I decide to keep it open. It would be better to be closed when the bug is located and fixed.

yssaya commented 5 years ago

I tried 30 times this position on my Win10 Pro 1809 with GTX 1050 Ti. But I could not reproduce error. aobaz.exe is basically single thread, but it uses one thread for GPU calculation. It might something thread timing error. We are planning to add more information to log file for next version. Thanks.