GNOME Bugzilla – Bug 618427
Swell-foop segfaults with error 4 in libclutter-glx-1.0.so.0.200.4
Last modified: 2011-04-20 17:42:52 UTC
In Ubuntu Lucid Stephen Keller reported: The gnome game swell-foop intermittently segfaults and leaves messages like this in the /var/log/messages: May 3 18:43:54 stephen-desktop kernel: [258657.370101] seed[16935]: segfault at 14 ip b2d815c5 sp bff888a8 error 4 in libclutter-glx-1.0.so.0.200.4[b2d5f000+d6000] Sometimes the game works without issue, but performance bogs down and then it dies unexpectedly. The machine was minimally loaded at the time.The gnome game swell-foop intermittently segfaults and leaves messages like this in the /var/log/messages: May 3 18:43:54 stephen-desktop kernel: [258657.370101] seed[16935]: segfault at 14 ip b2d815c5 sp bff888a8 error 4 in libclutter-glx-1.0.so.0.200.4[b2d5f000+d6000] Sometimes the game works without issue, but performance bogs down and then it dies unexpectedly. The machine was minimally loaded at the time. Launchpad ref: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-games/+bug/574876 Thanks!
Created attachment 163994 [details] swell-foop gdb swell-foop segfaulting under control of gdb
I encountered this bug, too. I commented out 2 lines. After that, SIGSEGV crash is not reproduced. In source [Board.js] -> in function [_connected_lights] // while(GLib.main_context_pending()) <-- commented out // GLib.main_context_iteration(); <-- commented out # I don't have any experience of gtk+ application development. # So I don't know what these API calls do, and why these APIs are needed. thanks.
I can't reproduce this. Can you reopen if you see this with 3.0.x or higher? Also, a complete stack trace (with debug symbols!) would be very helpful.