GNOME Bugzilla – Bug 162638
[alsasink] crash playing mp3 on a 64bit machine
Last modified: 2005-06-30 15:44:44 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: rhythmbox Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: crash playing mp3 Bugzilla-Product: rhythmbox Bugzilla-Component: playback Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: app crashes when apprempting to play an mp3 Steps to reproduce the crash: 1. start rhythmbox 2. add mp3s 3. select one, click play 4. app crashes Expected Results: should play mp3 file How often does this happen? every time Additional Information: running from a console does not produce any error output rhythmbox-0.8.8-2.1.fc3.rf Debugging Information: Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found)...Using host libthread_db library "/lib64/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 182979499680 (LWP 8861)] [New Thread 1128290656 (LWP 8868)] [Thread debugging using libthread_db enabled] [New Thread 182979499680 (LWP 8861)] [New Thread 1128290656 (LWP 8868)] [Thread debugging using libthread_db enabled] [New Thread 182979499680 (LWP 8861)] [New Thread 1128290656 (LWP 8868)] [New Thread 1126189408 (LWP 8867)] [New Thread 1115699552 (LWP 8865)] [New Thread 1105209696 (LWP 8864)] [New Thread 1094719840 (LWP 8863)] [New Thread 1084229984 (LWP 8862)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0000002a97a49b9f in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0
+ Trace 54033
Thread 2 (Thread 1128290656 (LWP 8868))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-31 14:30 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "rhythmbox". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was wasguru@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder. I'm going to move to GStreamer based on the stack trace.
I was able to fix this by changing the settings in gstreamer-properties. Output was set to Alsa, changing to OSS fixed the problem. There is no link to these settings from Rythmbox so it is not obvious to the user how or where to configure the soud output. Perhaps an error message instead of a crash would help too :)
Can you install debuggin symbols and provide me with a new backtrace? It appears to crash somewhere with alsa, but it's unclear if this is inside mad (which is illogical, but which the backtrace indicates) or inside alsa (which is logical, but it only appears lower in the trace).
I'd be happy to but you're going to have to tell me how & what to do.
install the -debug RPMs for gstreamer/gst-plugins and re-do what you did to get this stacktrace.
Ok got the debug rpms. I used the reporting tool to report the bug the first time. How can I capture the stacktrace without creating a new bug?
Run in gdb. When it crashes, type 'thread apply all bt'. See http://bugzilla.gnome.org/getting-traces.cgi also.
I'm expecting this to be a dup of #162184 btw, because of this bit:
+ Trace 54601
Leaving NEEDINFO until backtrace is provided.
bug 164911 may be a dupe...
I'm getting this on amd64 on Debian with gstreamer 0.8.7. Running with osssink works fine, but using alsasink causes a coredump. Here's the backtrace when running with: GST_DEBUG="alsa:5" gst-launch-0.8 filesrc location=/home/ari/test.mp3 ! mad ! alsasink LOG (0x50ac40 - 308042:53:13.425209000) alsa(18614) gstalsasink.c(380):gst_alsa_sink_loop:<alsasink0> pulled data 0x524830 from pad 0 LOG (0x50ac40 - 308042:53:13.425244000) alsa(18614) gstalsasink.c(385):gst_alsa_sink_loop:<alsasink0> pulled data 0x524830 is an event, checking LOG (0x50ac40 - 308042:53:13.425265000) alsa(18614) gstalsasink.c(209):gst_alsa_sink_check_event:<alsasink0> checking event 0x524830 of type 4 on sink pad 0 WARN (0x50ac40 - 308042:53:13.425288000) alsa(18614) gstalsasink.c(246):gst_alsa_sink_check_event:<alsasink0> couldn't extract time from discont event. Bad things might happen! LOG (0x50ac40 - 308042:53:13.425309000) alsa(18614) gstalsasink.c(257):gst_alsa_sink_check_event:<alsasink0> unreffing event 0x524830 of type 4 with refcount 1 DEBUG (0x50ac40 - 308042:53:13.428302000) alsa(18614) gstalsa.c(1063):gst_alsa_link: found format S16_LE INFO (0x50ac40 - 308042:53:13.428327000) alsa(18614) gstalsa.c(1449):gst_alsa_probe_hw_params: Probing format: S16_LE 44100Hz, 2 channels WARN (0x50ac40 - 308042:53:13.428915000) alsa(18614) gstalsa.c(1491):gst_alsa_probe_hw_params:<alsasink0> "snd_pcm_hw_params_set_period_size_near (this->handle, hw_params, &period_size, 0)": Invalid argument ERROR: from element /pipeline0/mad0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2563): gst_pad_set_explicit_caps: /pipeline0/mad0: failed to negotiate (try_set_caps with "audio/x-raw-int, endianness=(int)1234, signed=(boolean)true, width=(int)16, depth=(int)16, rate=(int)44100, channels=(int)2" returned REFUSED) Program received signal SIGFPE, Arithmetic exception.
+ Trace 55943
Thread 46912515205504 (LWP 18614)
That bug is fixed in CVS. Please re-try with CVS and let me know if it still reproduces (and if it does, provide me with a new backtrace so I can fix the actual bug).
CVS does indeed not crash anymore, but now I'm seeing what looks like Bug #165964.
Ari, can we close this?
yeah, I guess so.