A little more investigation shows that it uses 100% cpu whenever I start
a new game using the "new game" command.  The only way it uses a
reasonable amount of cpu is when I have ended a game on the previous
session, and the new session starts with the default game (human: white
vs. comp: black).

The 100% cpu usage persists on games started with "new game" even if I
restart the app, as long as I have made a move before restarting.  If I
haven't made a move, the "new game" is lost and the app restarts with
the default game, so it is impossible for me to play black without
having the 100% cpu.

The behaviour doesn't change in 3d mode.  (I am unable to make more than
one move in 3d mode due to another bug.)

As I mentioned, I am using Hardy.  I will be upgrading to Intrepid in
the next days.

I created a new user and the problem is the same.

I notice that the app spawns a new gnome-gnuchess process for every new
game, and those processes are the ones using all the cpu.  If I start
one "new game", and then start another, the system will have two gnome-
gnuchess processes running, each using 50% cpu.  WTF?

-- 
Chess uses 100% cpu only when I play black
https://bugs.launchpad.net/bugs/288593
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to