GNOME Bugzilla – Bug 602140
context: segfault from libwebkit or in python bindings?
Last modified: 2009-12-07 09:55:51 UTC
Was listening to some local mp3's and noticed Rhythmbox had randomly died. Restarted from inside a gdb session, and noticed the following crasher/hanger (apparently) from the context plugin. The currently playing song was 1 second away from changing to another song in the same auto playlist, by the same artist. Shuffle and repeat were not active. I have a feeling that 'Thread 28' is somehow the culprit. A gdb backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffce57f910 (LWP 14657)] 0x00007fffdf137d18 in ?? () from /usr/lib/libwebkit-1.0.so.2 (gdb) thread apply all bt
+ Trace 219137
Thread 28 (Thread 0x7fffce57f910 (LWP 14657))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
For your viewing pleasure, a stacktrace with webkit, gtk, and glib debug packages installed. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffcd93f910 (LWP 15385)] push_heap<WebCore::TimerHeapIterator> (this=<value optimized out>) at /usr/include/c++/4.4/bits/stl_heap.h:168 168 _ValueType __value = _GLIBCXX_MOVE(*(__last - 1)); Current language: auto The current source language is "auto; currently c++". (gdb) thread apply all bt
+ Trace 219138
Thread 22 (Thread 0x7fffcd93f910 (LWP 15385))
*** Bug 602974 has been marked as a duplicate of this bug. ***
If you enable crossfading it'll probably stop crashing.
fixed in commit e93fd2d7afe1411a5a60052a4adecd6a56db5b7b
*** Bug 603726 has been marked as a duplicate of this bug. ***
*** Bug 603945 has been marked as a duplicate of this bug. ***
*** Bug 603957 has been marked as a duplicate of this bug. ***