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 144510 - [ffmpeg - ima-adpcm-ws/wsaud] scheduler issues
[ffmpeg - ima-adpcm-ws/wsaud] scheduler issues
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.8.7
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 138435
 
 
Reported: 2004-06-17 04:00 UTC by Ronald Bultje
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ronald Bultje 2004-06-17 04:00:12 UTC
[forked from #134320 because that bug is a mess of various bug reports]

[..]

After fixing that, it still fails with scheduler assertions. No clue where to go
from there:

[rbultje@shrek gst-ffmpeg]$ ../gstreamer/tools/gst-launch filesrc
location=/tmp/chiptune.sog ! ffdemux_wsaud .audio_00 ! ffdec_adpcm_ima_ws !
audioconvert ! audioscale ! alsasink
RUNNING pipeline ...
Segmentation fault
[rbultje@shrek gst-ffmpeg]$ ../gstreamer/tools/gst-launch filesrc
location=/tmp/chiptune.sog ! spider ! audioconvert ! audioscale ! osssink
RUNNING pipeline ...
 
** ERROR **: file gstoptimalscheduler.c: line 704 (sort_chain): assertion
failed: (original == NULL)
aborting...
Aborted
[rbultje@shrek gst-ffmpeg]$ ../gstreamer/tools/gst-launch filesrc
location=/tmp/chiptune.sog ! ffdemux_wsaud .audio_00 ! ffdec_adpcm_ima_ws !
audioconvert ! audioscale ! alsasink
RUNNING pipeline ...
Segmentation fault
[rbultje@shrek gst-ffmpeg]$ ../gstreamer/tools/gst-launch filesrc
location=/tmp/chiptune.sog ! ffdemux_wsaud .audio_00 ! ffdec_adpcm_ima_ws !
audioconvert ! audioscale ! osssink
RUNNING pipeline ...
Execution ended after 2 iterations (sum 165792000 ns, average 82896000 ns, min
17000 ns, max 165775000 ns).

basicgthread goes to 100% CPU use, entrygthread just does nothing. What's
supposed to happen? Xine doesn't do anything either.

File link: http://bugzilla.gnome.org/attachment.cgi?id=27635&action=view
Comment 1 Ronald Bultje 2004-07-13 16:21:57 UTC
Adding original reporter to this bug as well.
Comment 2 Ronald Bultje 2004-12-19 01:07:55 UTC
This is fixed in the recent core release, I can no longer reproduce it. I now
get the same behaviour for this file on the commandline that I get for ffplay as
well. Totem has some small issues, but I'll get to fix those, too.