Hi there,
at the moment I test the x64 engines for the SWCR rating list. I have a little problem with Komodo 1.0 JA x64.
In SWCR the games ended with mate / remis (without resign or remis mode). End of the game (example: After mate) Komodo crashed from time to time in Shredder GUI tournament mode. The next game started with the next two engines. Komodo isn't in RAM. This is OK, but I have the crash message from the OS on the screen.
Now I try out a little bit. I used the same configuration (sample.per in UCI options field) compare to the 32-Bit version. Is the field of UCI options blank (without sample.per), no crashes and Komodo 1.0 JA x64 works fine.
With the 32-Bit version I have no problems. All works fine, also if I enter the sample.per in the field "UCI options".
I wonder, nobody have seen this after the release. But I think, I am the once with play the eng-eng games without resign mode up to mate.
Shredder 12 GUI
Windows XP Professional x64 Edition
The problem I have on three different PCs. All with Intel Q9550, and different 1.066 MHz RAMs, different Asus Mainboards but with exactly same OS configuration. 14 services are activ, no Virus scanner in RAM etc.. Only other driver for the three different Asus mainboards.
Best
Frank
PS: All other 15 x64 engines works fine, can't see a problem after 15 test games per engine. Perhaps Komodo need a OS service I deactivate, but I don't think so.
Komodo 1.0 JA x64 problem ...
Moderators: hgm, chrisw, Rebel
-
- Posts: 6837
- Joined: Wed Nov 18, 2009 7:16 pm
- Location: Gutweiler, Germany
- Full name: Frank Quisinsky
-
- Posts: 6837
- Joined: Wed Nov 18, 2009 7:16 pm
- Location: Gutweiler, Germany
- Full name: Frank Quisinsky
Re: Komodo 1.0 JA x64 problem ...
Hi there,
perhaps it helps, the services from OS Windows XP Prof. x64 Edition after system reboot. Systems have 2Gb RAM.
Two services are from Process Manager 12.02 (Microsoft tool):
Screen of Process Manager:
http://www.nk-qy.info/common/services.jpg
Best
Frank
perhaps it helps, the services from OS Windows XP Prof. x64 Edition after system reboot. Systems have 2Gb RAM.
Two services are from Process Manager 12.02 (Microsoft tool):
Screen of Process Manager:
http://www.nk-qy.info/common/services.jpg
Best
Frank
Last edited by Frank Quisinsky on Wed May 12, 2010 11:08 am, edited 1 time in total.
-
- Posts: 1539
- Joined: Thu Mar 09, 2006 2:02 pm
Re: Komodo 1.0 JA x64 problem ...
Hi Frank,
This problem happens when a game is finished. My guess is, that 10% of all games are causing an exception. ALL games are played and finished correctly, but when the GUI asks Komodo to leave the memory it crashes. It is not even the GUI who is giving the error, but Windows itself which is coming up with an error message which has to be confirmed with an OK click. After that "OK" the tourney continues automatically without any problems.
In my case this isn't that worse, as I have multiple GUI's running on ONE tourney, so the tourney itself was never stopped, but if you just run ONE GUI it waits and does nothing until you click "OK" to the Windows error message ... annoying!
Lets hope for the next release!
Bye
Ingo
It has nothing to do with the Etiquette setting (what you call 'resign mode'), it happens to me as well (Etiquette ON) and is reported to Don some weeks ago. He is for sure aware of that problem as I received some kind of confirmation email.Frank Quisinsky wrote:Hi there,
...
In SWCR the games ended with mate / remis (without resign or remis mode). End of the game (example: After mate) Komodo crashed from time to time in Shredder GUI tournament mode. The next game started with the next two engines. Komodo isn't in RAM. This is OK, but I have the crash message from the OS on the screen.
Now I try out a little bit. I used the same configuration (sample.per in UCI options field) compare to the 32-Bit version. Is the field of UCI options blank (without sample.per), no crashes and Komodo 1.0 JA x64 works fine.
With the 32-Bit version I have no problems. All works fine, also if I enter the sample.per in the field "UCI options".
I wonder, nobody have seen this after the release. But I think, I am the once with play the eng-eng games without resign mode up to mate.
This problem happens when a game is finished. My guess is, that 10% of all games are causing an exception. ALL games are played and finished correctly, but when the GUI asks Komodo to leave the memory it crashes. It is not even the GUI who is giving the error, but Windows itself which is coming up with an error message which has to be confirmed with an OK click. After that "OK" the tourney continues automatically without any problems.
In my case this isn't that worse, as I have multiple GUI's running on ONE tourney, so the tourney itself was never stopped, but if you just run ONE GUI it waits and does nothing until you click "OK" to the Windows error message ... annoying!
Lets hope for the next release!
Bye
Ingo
-
- Posts: 1539
- Joined: Thu Mar 09, 2006 2:02 pm
Re: Komodo 1.0 JA x64 problem ...
Hi
Bye
Ingo
I have the same OS, different services, 4 GB Memory, Etiquette on and the same problem. I am pretty sure it is a coding/compiling issue as all other engines on the same computers behave 'much less worse'. (With enough games nearly every engine will cause a crash sooner or later)Frank Quisinsky wrote:Hi there,
perhaps it helps, the services from OS Windows XP Prof. x64 Edition after system reboot. Systems have 2Gb RAM.
Two services are from Process Manager 12.02 (Microsoft tool):
Screen of Process Manager:
http://www.nk-qy.info/common/services.jpg
Best
Frank
Bye
Ingo
-
- Posts: 6837
- Joined: Wed Nov 18, 2009 7:16 pm
- Location: Gutweiler, Germany
- Full name: Frank Quisinsky
Re: Komodo 1.0 JA x64 problem ...
Hi Ingo,
thanks for the explanation !!
Perhaps a random that I don't have, after 15 additional test games, the OS error message on the screen without enter "sample.per" in the UCI options field.
Do the same you do with Shredder tournaments. No problems here if I config one tournament and the others PCs used the same Shredder tournament *.sto file via network. Only bad that from time to time the error message is on the screen.
A good solution is to stop the OS service which create the error message. I don't know.
Best
Frank
thanks for the explanation !!
Perhaps a random that I don't have, after 15 additional test games, the OS error message on the screen without enter "sample.per" in the UCI options field.
Do the same you do with Shredder tournaments. No problems here if I config one tournament and the others PCs used the same Shredder tournament *.sto file via network. Only bad that from time to time the error message is on the screen.
A good solution is to stop the OS service which create the error message. I don't know.
Best
Frank