GNOME Bugzilla – Bug 556253
crash in Rhythmbox Music Player: closing rhythmbox after ...
Last modified: 2009-10-30 05:49:33 UTC
Version: 0.11.6 What were you doing when the application crashed? closing rhythmbox after changing some tags Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 615690240 vsize: 615690240 resident: 94126080 share: 23187456 rss: 94126080 rss_rlim: 18446744073709551615 CPU usage: start_time: 1223984238 rtime: 2033 utime: 1736 stime: 297 cutime:0 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0x7fd27dc8b7a0 (LWP 16795)] 0x00007fd27cef75ef in waitpid () from /lib/libpthread.so.0
+ Trace 208147
Thread 1 (Thread 0x7fd27dc8b7a0 (LWP 16795))
----------- .xsession-errors (173000 sec old) --------------------- SwScaler: reducing / aligning filtersize 1 -> 4 SwScaler: reducing / aligning filtersize 5 -> 4 SwScaler: reducing / aligning filtersize 1 -> 1 SwScaler: reducing / aligning filtersize 5 -> 4 [swscaler @ 0xb2aad0]BICUBIC scaler, from yuv410p to rgb32 using MMX2 [swscaler @ 0xb2aad0]using 4-tap MMX scaler for horizontal luminance scaling [swscaler @ 0xb2aad0]using 4-tap MMX scaler for horizontal chrominance scaling [swscaler @ 0xb2aad0]using n-tap MMX scaler for vertical scaling (BGR) [swscaler @ 0xb2aad0]using MMX YV12->BGR32 Converter [swscaler @ 0xb2aad0]320x176 -> 320x176 VO: [x11] 320x176 => 320x176 BGRA A: 0.1 V: 0.0 A-V: 0.063 ct: 0.000 0/ 0 ??% ??% ??,?% 0 0 A: 0.1 V: 0.1 A-V: 0.060 ct: 0.000 0/ 0 ??% ??% ??,?% 1 0 A: 0.1 V: 0.1 A-V: 0.001 ct: 0.0 Exiting... (Quit) A: 4.8 V: 4.8 A-V: 0.042 ct: -0.034 0/ 0 1% 3% 1.8% 1 0 A: 4.8 V: 4.9 A-V: -0.035 ct: -0.035 0/ 0 1% 3% 1.9% 1 0 A: 4.9 V: 4.9 A-V: -0.010 ct: -0.0 ...Too much output, ignoring rest... --------------------------------------------------
The function rhythmdb_query_model_reapply_query_cb is called on a timer about every 30 minutes. It's possible that it was called as rhythmbox was exiting so its RhythmDBQueryModel parameter was invalid.
No, the timeout used to do that is removed when the query model is disposed.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 418163 ***