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 634620 - Rendering video in WebM muxer causes memory leak when settings are changed
Rendering video in WebM muxer causes memory leak when settings are changed
Status: RESOLVED INCOMPLETE
Product: pitivi
Classification: Other
Component: Rendering
0.13.5
Other Linux
: Normal critical
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-11 19:05 UTC by Kyle Bentley
Modified: 2011-08-19 04:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Kyle Bentley 2010-11-11 19:05:17 UTC 
Rendering a video with the stock settings works fine.  When the parameter under the video codec settings is changed to "encode on last pass of multi-pass" is selected, 8 GB of system memory are used within a few seconds.  This does not happen when "encode on first pass of multi-pass" is selected
Comment 1 Kyle Bentley 2010-11-14 17:14:28 UTC 
If I set the encode to "encode on the first pass", start the encoding process, cancel, and then change the encoding scheme to "encode on the last pass" everything continues as normal.
Comment 2 Jean-François Fortin Tam 2010-11-26 04:40:31 UTC 
Hmmm, could this be due to bug #603070 ? But at the same time, I guess it surely shouldn't cause a giant memory leak... Pitivi issue or gstreamer issue?
Comment 3 Jean-François Fortin Tam 2011-05-25 15:05:52 UTC 
I'm unable to reproduce this on pitivi git.

If I only set "encode on last pass of multi-pass", the render process simply sits there but the RAM usage doesn't go up. Instead, I get this in the terminal:


ERROR [18990] [0x   -48737940] "<Pipeline at 0x9e5c44c>"        pipeline          May 25 11:03:44      _handleErrorMessage: error from /GstPipeline:pipeline1/GstBin:bin7/GstBin:bin8/GstBin:bin9/GstVP8Enc:vp8enc0 (__main__.GstVP8Enc): Could not open resource for reading. (gstvp8enc.c(770): gst_vp8_enc_handle_frame (): /GstPipeline:pipeline1/GstBin:bin7/GstBin:bin8/GstBin:bin9/GstVP8Enc:vp8enc0:
Failed to open file '': No such file or directory) (pitivi/pipeline.py:852)


Which means that I did not specify a pass cache file in the setting right below.

Can you reproduce the memory usage problem? Otherwise I'm tempted to simply say "multi pass encoding sucks and that's a duplicate of bug #603070".
Comment 4 Akhil Laddha 2011-07-07 05:30:58 UTC 
Kyle Bentley, can you still reproduce the problem ? Please respond to comment#3.
Comment 5 Akhil Laddha 2011-08-19 04:54:04 UTC 
Please feel free to reopen the bug if you still face the problem with pitivi 0.14.0 or later.