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 135285 - weird things when playing buggy mp3 file
weird things when playing buggy mp3 file
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: dont know
0.8.0
Other Linux
: Normal normal
: 0.8.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-02-24 13:56 UTC by Stewart Jeacocke
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description Stewart Jeacocke 2004-02-24 13:56:57 UTC
Gstreamer always crashes with a SIGSEGV when playing this file:
http://www.jeacocke.org.uk/2003/ossdev/crashes_gstreamer_0_6_4.mp3

I'm running Debian and gstreamer 0.6.5 isn't in unstable yet so I can't 
test the file with your new release. Could someone who uses 0.6.5 test and 
see if this file still crashes gstreamer?

This is the command that I executed:

stewart@orb:~$ gst-launch filesrc location="crashes_gstreamer_0_6_4.mp3" ! 
mad ! osssink

INFO ( 4734: 0) Initializing GStreamer Core Library version 0.6.4
INFO ( 4734: 0) CPU features: (00000762) MMX SSE 3DNOW MMXEXT
INFO ( 4734: 0) registry: loaded global_registry in 0.147870 seconds
          (/var/lib/gstreamer/0.6/registry.xml)
GStreamer-INFO: 0 live buffer(s)
GStreamer-INFO: 0 live bufferpool(s)
GStreamer-INFO: 0 live event(s)
RUNNING pipeline
Caught SIGSEGV accessing address 0x8
  • #0 wait
    from /lib/tls/libpthread.so.0
  • #1 ??

Comment 1 David Schleef 2004-03-09 20:47:43 UTC
The mp3 file is buggy.

It doesn't crash HEAD.  mad doesn't play it fully.  ffdec_mp3 skips
over the bad parts.
Comment 2 Ronald Bultje 2004-04-15 03:30:46 UTC
So what am I supposed to do here? Make it magically work? ;).

Can I close this?
Comment 3 David Schleef 2004-04-15 03:43:16 UTC
I left it open, because mad was doing some really dumb stuff with it.  Not that
I actually wrote that on the bug.  Anyway, I think another related bug was
recently fixed in mad that may have fixed this one as well.  We should keep the
file around for testing, but otherwise, consider this closed.