After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676529 - glchess doesn't quit engine on exit
glchess doesn't quit engine on exit
Status: RESOLVED FIXED
Product: gnome-games-superseded
Classification: Deprecated
Component: glchess
trunk
Other Linux
: Normal normal
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
: 677037 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-05-21 22:42 UTC by Robert Ancell
Modified: 2013-05-01 21:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Ancell 2012-05-21 22:42:50 UTC 
From bug #675434:

Once glchess has lost on time, closing the program leaves a copy of gnuchess
running - it's taking almost the entire CPU of one core on my PhenomX4, that
residual program has run for half an hour without exiting, it has to be aborted
by killing the process in the system monitor.
Comment 1 Thomas Andersen 2012-05-22 23:33:54 UTC 
(at some point it might make sense to look at GSubprocess for this: https://bugzilla.gnome.org/show_bug.cgi?id=672102 )
Comment 2 Robert Ancell 2012-05-22 23:51:16 UTC 
That is *exactly* what I've been wanting from GLib.  I am going to be using that class like crazy.
Comment 3 Oren Held 2012-07-13 16:02:03 UTC 
Confirming that glchess leaves an extra cpu+mem hungry gnuchess process.
It happens both after each game, but also after quitting or after starting a new game in a single glchess run.

glchess v3.4.2, non-3D mode (old hardware), Debian unstable.
Comment 4 Robert Ancell 2012-07-14 05:18:14 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

It now kills the engines but engines still stick around if chess crashes. They should quit themselves in this case because their stdin will close.
Comment 5 Michael Catanzaro 2013-05-01 21:42:02 UTC 
*** Bug 677037 has been marked as a duplicate of this bug. ***