GNOME Bugzilla – Bug 347720
[mad] crashes rhythmbox in memcpy
Last modified: 2006-11-10 00:16:23 UTC
What were you doing when the app crashed?: skipping a currently playing song; current playlist was random selection from a mounted ipod mini (4g) current song skipped a little (hadnt dont that before), seletct next song, rhythmbox crashed Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.4 2006-07-11 (Ubuntu) BugBuddy Version: 2.15.0 Memmory status: size: 135561216 vsize: 0 resident: 135561216 share: 0 rss: 36245504 rss_rlim: 0 CPU usage: start_time: 1153092741 rtime: 0 utime: 9033 stime: 0 cutime:8684 cstime: 0 timeout: 349 it_real_value: 0 frequency: 5 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228289856 (LWP 17107)] [New Thread -1261823072 (LWP 23959)] [New Thread -1291445344 (LWP 23956)] [New Thread -1278608480 (LWP 17127)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 69376
Thread 2 (Thread -1261823072 (LWP 23959))
The crash is inside the 'mad' element, so moving to GStreamer. I'm fairly certain I've seen backtrace like that before, so it's probably a dupe, but I can't find any bugs with the same backtrace.
Everything from this bit down looks messed up to me:
+ Trace 69378
The thread with the signal handler call in it was thread 2, not that one:
+ Trace 69379
*** Bug 347859 has been marked as a duplicate of this bug. ***
*** Bug 347974 has been marked as a duplicate of this bug. ***
- can anyone reproduce this reliably? - is there a specific song this happens with or does it happen randomly? - is anyone able to reproduce this with full debugging symbols? (ubuntu users should install the gstreamer0.10-plugins-ugly package)
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Tim-Philipp asked for. Thanks for any help!