From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041009 Firefox/1.0 Description of problem: Closing gataxx doesn't actually stop it running (it just makes the window go away). This lets gataxx effectively run forever (even after the user logs out of X). (after launching from a terminal) gataxx has a double free bug and the glibc detection code is catching it but not letting the program die. Version-Release number of selected component (if applicable): gnome-games-2.8.0-4 How reproducible: Always Steps to Reproduce: 1. Start a gnome-terminal . 2. Run gataxx . 3. Click the close button at the top right. Actual Results: *** glibc detected *** double free or corruption (!prev): 0x09783f98 *** Expected Results: gataxx to quit. Additional info: Valgrind log to come.
Created attachment 111687 [details] Valgrind log showing double free Problem seems to be around gtkgridboard.c:218 ==9430== Invalid free() / delete / delete[] ==9430== at 0x1B902FB1: free (vg_replace_malloc.c:153) ==9430== by 0x804CF9F: gtk_gridboard_destroy (gtkgridboard.c:218) ==9430== Address 0x1BDD7A30 is 0 bytes inside a block of size 224 free'd ==9430== at 0x1B902FB1: free (vg_replace_malloc.c:153) ==9430== by 0x804CF9F: gtk_gridboard_destroy (gtkgridboard.c:218)
Created attachment 111688 [details] Valgrind log showing double free Problem seems to be around gtkgridboard.c:218 ==9430== Invalid free() / delete / delete[] ==9430== at 0x1B902FB1: free (vg_replace_malloc.c:153) ==9430== by 0x804CF9F: gtk_gridboard_destroy (gtkgridboard.c:218) ==9430== Address 0x1BDD7A30 is 0 bytes inside a block of size 224 free'd ==9430== at 0x1B902FB1: free (vg_replace_malloc.c:153) ==9430== by 0x804CF9F: gtk_gridboard_destroy (gtkgridboard.c:218)
Created attachment 111689 [details] Valgrind log showing double free
Created attachment 111690 [details] Valgrind log showing double free
Agh! I was getting internal errors from bugzilla which is why I submitted the above again. I apologise for the duplicate entry.
This appears to have been fixed in FC4's gnome-games-2.10.0-5
Hi, Great, thanks.