colbyga / pychess

Automatically exported from code.google.com/p/pychess
GNU General Public License v3.0
0 stars 0 forks source link

Pychess crashing when quitting a game agains an AI #383

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start a game against an AI
2. quit the game during the game.
3. click close without saving

What is the expected output? What do you see instead?

The game must be quit, but not pychess.

Does it happen every time?

No, but frequently enough to be annoying

What version of the product are you using?

read only svn repo of 27/01/09 15:13

Did you use an installed version of PyChess or did you run in from a
tarball/svn?

from the read only svn repo of 27/01/09 15:13

Please provide any additional information below.

Please attach the latest pychess logfile.
For PyChess <= 0.6.x it's hidden in your homedirectory and called
".pychess.log".
For PyChess > 0.6.x, it's in a hidden folder, under your homedirectory,
named ".pychess/"

Original issue reported on code.google.com by cabu...@gmail.com on 28 Jan 2009 at 1:12

Attachments:

GoogleCodeExporter commented 9 years ago
Can you tell me witch distribution and processor you use?

Original comment by lobais on 2 Feb 2009 at 10:03

GoogleCodeExporter commented 9 years ago
The log is from a Athlon 64 X2 3600+ running Window XP Pro 32bits with 
Virtualbox
2.1.2 running Ubuntu 8.10. But I have the same problem with Ubuntu 8.10 on an 
Athlon
64 X2 4400+. The problem is more frequent under Virtualbox than on the 'true' 
hardware.

Original comment by cabu...@gmail.com on 3 Feb 2009 at 4:31

GoogleCodeExporter commented 9 years ago
Hm, I can't reproduce it from ubuntu under virtualbox as well as true hardware.
Perhaps it was related to issue 381.. Do you mind updating again?
In what way do you end the game? By Ctrl+W or by clicking the button in the tab?

Original comment by lobais on 5 Feb 2009 at 6:43

GoogleCodeExporter commented 9 years ago
I do it by clicking the button in the tab.
I don't think it is related to 381 due to the fact that the problem could be 
triggred
by quitting a game watever the game is finished or not.

Original comment by cabu...@gmail.com on 7 Feb 2009 at 11:30

GoogleCodeExporter commented 9 years ago
I see, but please try again with trunk. The fixes which have been to engine 
handling
might affact other stuff as well.
Or can you reproduce this in a human vs. human game with no analyzers?

Original comment by lobais on 9 Feb 2009 at 4:15

GoogleCodeExporter commented 9 years ago

Original comment by gbtami on 19 Mar 2009 at 8:15

GoogleCodeExporter commented 9 years ago

Original comment by lobais on 11 Mar 2011 at 4:41