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 653582 - ximagesrc: unbounded memory usage
ximagesrc: unbounded memory usage
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.25
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 653709
 
 
Reported: 2011-06-28 19:02 UTC by david.crepps
Modified: 2011-08-10 00:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description david.crepps 2011-06-28 19:02:34 UTC
When using the use-damage=false option with ximagesrc, I frequently see rapidly-growing memory usage for that application.  It only appears when a pipeline actually hands the raw video to an encoder, but it doesn't seem like it is reproduced reliably every time.

I'm using the following launch call to demonstrate the error:

gst-launch ximagesrc use-damage=false ! queue ! ffmpegcolorspace ! ffenc_flv bitrate=5000000 ! flvmux ! filesink location=/local/test.flv

I've definitely witnessed it on ffenc_flv, ffenc_mpeg4, and ffenc_h263p, especially at higher bitrates.  Unfortunately, it doesn't always occur given the same call, but if you play around with slightly different pipelines, it eventually pops up.  I'm running on a RHEL 5.3 machine, running gstreamer 0.10.30 and ximagesrc 0.10.25, fwiw.

To see the symptoms, I've been running "top", and noticing the rapid growth of memory usage in both the gst-launch process and the Xorg process.  Once it gets to 100% memory usage, the machine gets hopelessly locked up and requires the one-finger salute.

Thanks,
Dave
Comment 1 David Schleef 2011-06-30 04:49:55 UTC
ximagesrc really should not be marking every second buffer as DISCONT.  This may or may not be related to the problem here.

Your gstreamer package versions are quite old.  I'm not sure we can really do anything about this unless the bug is reproduced on recent versions.
Comment 2 Fabio Durán Verdugo 2011-08-10 00:12:27 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!