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 162184 - [PATCH] [mad] crash playing a mp3 file
[PATCH] [mad] crash playing a mp3 file
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: dont know
0.8.7
Other other
: Normal normal
: 0.8.8
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 162760 (view as bug list)
Depends on:
Blocks: 138435
 
 
Reported: 2004-12-24 19:20 UTC by simo.ragnetti
Modified: 2005-01-19 11:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Attachments
patch (727 bytes, patch)
2004-12-25 02:53 UTC, David Schleef
none Details | Review
Output of gdb amarokapp with env. var. GST_DEBUG="mad:5" (156.48 KB, text/plain)
2005-01-18 10:26 UTC, Francois Kritzinger
  Details
possible fix (1.92 KB, patch)
2005-01-18 12:44 UTC, Ronald Bultje
none Details | Review

Description simo.ragnetti 2004-12-24 19:20:23 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-utils
Severity: normal
Version: GNOME2.8.0 0.8.8
Gnome-Distributor: Red Hat, Inc
Synopsis: when with Rhytmbox i play an mp3, it crash...
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 0.8.8
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1.  open rhythmbox
2. play any mp3 files
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/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)...[Thread debugging using
libthread_db enabled]
[New Thread -151151872 (LWP 23941)]
[New Thread 19176368 (LWP 23947)]
[Thread debugging using libthread_db enabled]
[New Thread -151151872 (LWP 23941)]
[New Thread 19176368 (LWP 23947)]
[Thread debugging using libthread_db enabled]
[New Thread -151151872 (LWP 23941)]
[New Thread 19176368 (LWP 23947)]
[New Thread 55585712 (LWP 23945)]
[New Thread 45095856 (LWP 23944)]
[New Thread 34606000 (LWP 23943)]
[New Thread 109579184 (LWP 23942)]
0x003087a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 2 (Thread 19176368 (LWP 23947))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __udivdi3
    from /usr/lib/gstreamer-0.8/libgstmad.so
  • #5 gst_mad_chain
    at gstmad.c line 1422
  • #6 gst_pad_call_chain_function
    at gstpad.c line 4430
  • #7 gst_pad_push
    at gstpad.c line 3241
  • #8 gst_id3_tag_chain
    at gstid3tag.c line 1254
  • #9 gst_pad_call_chain_function
    at gstpad.c line 4430
  • #10 gst_pad_push
    at gstpad.c line 3241
  • #11 gst_spider_identity_chain
    at gstspideridentity.c line 222
  • #12 loop_group_schedule_function
    at gstoptimalscheduler.c line 1332
  • #13 gst_opt_scheduler_schedule_run_queue
    at gstoptimalscheduler.c line 1154
  • #14 gst_opt_scheduler_get_wrapper
    at gstoptimalscheduler.c line 1451
  • #15 gst_pad_pull
    at gstpad.c line 3296
  • #16 gst_spider_identity_dumb_loop
    at gstspideridentity.c line 448
  • #17 loop_group_schedule_function
    at gstoptimalscheduler.c line 1332
  • #18 gst_opt_scheduler_schedule_run_queue
    at gstoptimalscheduler.c line 1154
  • #19 gst_opt_scheduler_get_wrapper
    at gstoptimalscheduler.c line 1451
  • #20 gst_pad_pull
    at gstpad.c line 3296
  • #21 gst_alsa_sink_loop
    at gstalsasink.c line 378
  • #22 loop_group_schedule_function
    at gstoptimalscheduler.c line 1332
  • #23 gst_opt_scheduler_schedule_run_queue
    at gstoptimalscheduler.c line 1154
  • #24 gst_opt_scheduler_iterate
    at gstoptimalscheduler.c line 1258
  • #25 gst_scheduler_iterate
    at gstscheduler.c line 738
  • #26 gst_bin_iterate_func
    at gstbin.c line 1220
  • #27 gst_marshal_BOOLEAN__VOID
    at gstmarshal.c line 509
  • #28 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #33 gst_bin_iterate
    at gstbin.c line 1280
  • #34 gst_thread_main_loop
    at gstthread.c line 671
  • #35 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #36 start_thread
    from /lib/tls/libpthread.so.0
  • #37 clone
    from /lib/tls/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-24 14:20 -------


Unknown version 0.8.8 in product gnome-utils.  Setting version to "unspecified".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-utils".
   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 simo.ragnetti@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.

Comment 1 Elijah Newren 2004-12-24 19:52:22 UTC
I belive from the stack trace this should be assigned to gstreamer...let me know
if I was wrong.
Comment 2 Elijah Newren 2004-12-24 19:53:50 UTC
Oops, that was supposed to be version 0.8.7 (the version that comes with Fedora
3), not 0.6.0...
Comment 3 David Schleef 2004-12-25 02:53:19 UTC
Created attachment 35197 [details] [review]
patch

A potential patch.  I'm not checking this in, because it's not clear to me why
mad->rate would be used.
Comment 4 Ronald Bultje 2004-12-30 10:38:20 UTC
This can happen indeed when we haven't synced yet. The above patch is not right.
The correct thing is to return out of the chain function until mad->rate is set
(see _caps_reset()).
Comment 5 Ronald Bultje 2005-01-17 10:34:32 UTC
*** Bug 162760 has been marked as a duplicate of this bug. ***
Comment 6 Ronald Bultje 2005-01-17 10:41:11 UTC
Can any of the people who can reproduce this please provide me with a
GST_DEBUG=mad:5 log? Set the environment variable GST_DEBUG to "mad:5" and run
whatever command you did to get this crash, and redirect the output to some file
and attach the file here.

Thanks.
Comment 7 Francois Kritzinger 2005-01-18 10:26:50 UTC
Created attachment 36165 [details]
Output of gdb amarokapp with env. var. GST_DEBUG="mad:5"
Comment 8 Ronald Bultje 2005-01-18 12:44:57 UTC
Created attachment 36171 [details] [review]
possible fix

I think this is the correct patch. If I read the log correctly, negotiation
(during crossfading) fails, and that causes a subsequent SIGFPE. That's
actually an amarok bug, but we should not crash. Rather, we should safely error
out, like this patch tries to do.

Please test and see if this patch fixes the crashes and returns a proper error
instead.
Comment 9 Eric Shattow 2005-01-19 00:40:24 UTC
I was receiving "Illegal instruction" from the gst-plugins-mad 0.8.5, and
upgrading to gst-plugins-mad 0.8.7 seems to remedy my trouble. The userland
application that makes use of gst-plugins-mad for me is Rhythmbox, on Gentoo
Linux distro.
Comment 10 Ronald Bultje 2005-01-19 11:01:24 UTC
Francois, if you have some time, please test this. Also for the others. I'm
marking this fixed, I just applied the patch. Please let me know if, after using
this patch, you still do get SIGFPEs, and I'll continue debugging this.