After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 481861 - crash in Rhythmbox Music Player: Playing "Osira" from Jam...
crash in Rhythmbox Music Player: Playing "Osira" from Jam...
Status: RESOLVED DUPLICATE of bug 482819
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-30 12:37 UTC by stephan
Modified: 2007-10-05 11:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description stephan 2007-09-30 12:37:41 UTC
Version: 0.11.2

What were you doing when the application crashed?
Playing "Osira" from Jamendo (through Jamendo plugin) while importing some GB of music into the library.

BTW: Does Bug Buddy handle Gentoo's splitdebug feature?


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.3 2007-09-05 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.23-rc6-gc5a3f8e7 #2 SMP PREEMPT Wed Sep 19 22:56:57 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 885194752 vsize: 885194752 resident: 199684096 share: 24236032 rss: 199684096 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191154812 rtime: 9624 utime: 9157 stime: 467 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47535712484752 (LWP 6492)]
[New Thread 1132505424 (LWP 6810)]
[New Thread 1157683536 (LWP 6809)]
[New Thread 1124112720 (LWP 6808)]
[New Thread 1115720016 (LWP 6807)]
[New Thread 1098934608 (LWP 6806)]
[New Thread 1140898128 (LWP 6804)]
[New Thread 1107327312 (LWP 6801)]
[New Thread 1090541904 (LWP 6497)]
0x00002b3bbe255adf in __libc_waitpid (pid=6838, stat_loc=0x7ffff16c59ac, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 47535712484752 (LWP 6492))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 ??
  • #4 g_source_callback_unref
    at gmain.c line 1182
  • #5 g_source_destroy_internal
    at gmain.c line 961
  • #6 IA__g_main_context_dispatch
    at gmain.c line 2086
  • #7 g_main_context_iterate
    at gmain.c line 2694
  • #8 IA__g_main_loop_run
    at gmain.c line 2898
  • #9 IA__gtk_main
    at gtkmain.c line 1144
  • #10 main
    at main.c line 306


----------- .xsession-errors (27797308 sec old) ---------------------
==========================================================================
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==========================================================================
AO: [oss] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 512 x 384 (preferred colorspace: Planar YV12)
Opening video filter: [pp]
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [xv] 512x384 => 512x384 Planar YV12  [zoom]
A:   0.1 V:   0.0 A-V:  0.149 ct:  0.000   1/  1 ??% ??% ??,?% 0 0 2%           
A:   0.2 V:   0.0 A-V:  0.196 ct:  0.002   2/  2 ??% ??% ??,?% 0 0 61%          
A:   0.3 V:   0.1 A-V:  0.176 ct:  0.0
A:   8.5 V:   8.6 A-V: -0.012 ct:  0.021 206/206 12% 23%  2.1% 8 0 88%          
A:   8.6 V:   8.6 A-V:  0.007 ct:  0.022 207/207 12% 22%  2.1% 8 0 88%          
A:   8.6 V:   8.6 A-V:  0.008 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-05 11:05:39 UTC
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.

re. splitdebug, bug-buddy just uses gdb to generate the stack trace, so as long as splitdebug works with gdb, it'll be OK.

*** This bug has been marked as a duplicate of 482819 ***