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 300200 - cpu usage on certain .mov file goes to 100% once file has finished playing (memory usage also increases a lot)
cpu usage on certain .mov file goes to 100% once file has finished playing (m...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-libav
git master
Other Linux
: Normal normal
: 0.8.5
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-11 14:48 UTC by Gentoo's GStreamer Bug Tracker
Modified: 2005-04-14 10:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gentoo's GStreamer Bug Tracker 2005-04-11 14:48:43 UTC
can reproduce on totem, but not on playbin from command line, so assumed totem
specific

Gentoo bug ref: http://bugs.gentoo.org/show_bug.cgi?id=86042

Mov file can be d/led here:
http://www.tliquest.net/allmarksoftware/downloads/videos/gates.mov
Comment 1 Michaël Arnauts 2005-04-11 15:53:11 UTC
Ow yeah, defenitly reproducable with totem/gstreamer/gstplugins-cvs.
I just recovered from pressing crtl+alt+sysrq+sub...

I've analysed the problem a bit more, when the movie is almost done, the
framerate goes down a lot, to about one frame per two seconds. After that, totem
uses 100% cpu. When i want to close totem afterwards, it starts sucking memory
and you need to be quick to kill it.
Comment 2 Ronald Bultje 2005-04-11 16:18:21 UTC
May be ALSA-related, I've fixed such issues in our ALSA plugin before. Is it
reproduceable with osssink as audio output?
Comment 3 Gentoo's GStreamer Bug Tracker 2005-04-11 16:24:54 UTC
I get the memory usage heavy increase once playing finished but not the cpu
usage, and the system is still very very sluggish until i kill totem, with
osssink as the audio output.
Comment 4 Ronald Bultje 2005-04-14 10:22:11 UTC
OK, something (I'm not sure what yet) is sending out data with broken
timestamps. Probably the video stream, but I don't see any frames. Anyway, this
goes on until 30 minutes, for data that does not exist. That is completely
broken. At some point, ALSA decides that the audio/video are too far off and
stops a/v sync (that causes the hiccups in playback initially), which will cause
the 100% CPU use (continuous non-synced handling of non-existing video frames).

What happens after that is unclear. It eats memory, but I haven't been able to
see why yet, it hangs my system completely. :-(.
Comment 5 Ronald Bultje 2005-04-14 10:29:12 UTC
Hm, it seems ffmpeg's cinepak decoder goes into an endless loop to decode video
frames on EOS (where it flushes the remaining cached frames, for B-frame
movies). Continuously decoding the last frame. Ewh. The play->pause will
release_locks, thereby continuously adding data to the queue which ffmpeg
endlessly produces. This is a bug in ffmpegdec, which also explains the rest.
Comment 6 Ronald Bultje 2005-04-14 10:50:50 UTC
Added workaround to ffmpegdec. The rest is up-to-upstream.