search

google-code-export / pychess

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

PyChess gets unstable after a game has been closed #347

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start a game
2. Close it on the X
3. Aggressively press some UI component, like a menuitem.

What is the expected output? What do you see instead?
Half of the time PyChess crashes with something like
"08294e73-c174-0861-392610b8-223251f7 is dumped"
The other half it just spits a lot of strange warnings out:
"Main.py:228: Warning: instance of invalid non-instantiatable type
`(null)'" or "python: xcb_io.c:120: process_responses: Assertion
(assertion) '!(req && current_request && !((int) ((req->sequence) -
(current_request)) <= 0))' failed."

While no games has been closed yet (none started or just still running)
everything is as stable as a rock.

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

Original issue reported on code.google.com by lobais on 20 Sep 2008 at 1:03

GoogleCodeExporter commented 9 years ago 
It might be a gtkbug, but it seams to work after I changed the widget.unparent()
calls, in gamewidget, with parent.remove(widget) calls.

Original comment by lobais on 20 Sep 2008 at 7:20