Am Dienstag, den 03.09.2013, 09:34 +0200 schrieb Sebastian Dröge: > On Mo, 2013-09-02 at 17:58 +0200, Steffen Kieß wrote: > > Package: libgstreamer-plugins-bad0.10-0 > > Version: 0.10.23-7.1 > > Severity: important > > > > gstreamer runs into an endless loop when reading some files. This e.g. will > > cause /usr/lib/rhythmbox/rhythmbox-metadata to generate 100% CPU load > > without > > doing anything when encoutering such files. > > Can you check if this also happens with GStreamer 1.0, i.e. when running > gst-discoverer-1.0 from gstreamer1.0-plugins-base-apps after installing > gstreamer1.0-plugins-bad?
Yes, this also happens with gstreamer1.0-plugins-bad:amd64=1.0.7-1 (current version from testing) and gstreamer1.0-plugins-bad:amd64=1.0.10-2 (current version from unstable). The problem does not occur with gstreamer1.0-plugins-bad:amd64=1.1.4-2 (from experimental): root@debian:/tmp# gst-discoverer-1.0 file Analyzing file:///tmp/file Done discovering file:///tmp/file An error was encountered while discovering the file No valid frames found before end of stream root@debian:/tmp# > > Also can you make such a file available for testing? I've attached a test file.
testfile
Description: Binary data
