High memory usage - Githubissues

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?

1. Start flowblade
2. After approximately 30-40mins I started to notice a (I guess) unusual high 
memory usage
3. The longer flowblade is running, the more memory it uses/consumes - up to 
the point till it "eats" up all the available memory and then it starts to use 
the swap-partition (after some time with the same result)  

What is the expected output? What do you see instead?

On my system this is always reproducible. First I thought it had something 
something to do with the amount of mediafiles I'm using in my editing-projects 
(mostly MPEG2 and sometimes lossless HuffYUV), but it also happens when I only 
start flowblade and leave it running in the background without opening any 
projects or adding files.

For example I started flowblade today at 18:45 and it used +/- 210MB of memory 
and then at 

- 18:50: 300MB
- 18:55: 400MB
- 19:05: 700MB
- 19:15: 1000MB
- 19:25: 1300MB
- 19:35: 1500MB

and this continues till no more memory and swap is available on my PC. I've 
attached several pmap-analyses to this report and also txt-files that include 
the output of starting flowblade in a terminal and my hardware-specs. 

What version of the product are you using? On what operating system?
MLT found, version: 0.9.2
OS: Fedora 21 (Twenty One) 64bit
Python 2.7.8 (default
GCC 4.9.2 20141101 (Red Hat 4.9.2-1)]
GTK+ version: (2, 24, 25)
Locale: de_AT

- frei0r-plugins 1.4
- ffmpeg 2.4.6

I'm using the free nouveau-driver with a Nvidia G210 graphics card, 4GB of 
DDR3-Memory and a rather slow AMD II X2 270. The detailed specs of my PC-system 
are available in the hardware.txt-file. 

Please provide any additional information below.

Sadly I wasn't able to figure out what could cause the more and more increasing 
memory-usage, but please let me know if I you need any more information about 
this - I would be very glad to help whereever I can and if it's possible for 
me. At the moment I'm using Flowblade till the memory-usage gets to high 
(usually 40-50 mins) and then I close and open it again. Other than the high 
memory usage there are no other "side-effects" at all and flowblade works 
flawlessly for me.  

Now and most important: Let me say a big, big thank you for the truly amazing 
piece of software you've created with flowblade. Over the years I've tested 
many of the available videoeditors available for Linux, but flowblade was the 
first one that has really and highly impressed me. First of all and compared to 
most others available in Linux it's very stable (most important for me), offers 
all I need in a video-editor and much, much more. You've done a tremendous job 
and imho this very fine video-editor deserves much more attention in the 
"Linux-world". Thank you so much!

Original issue reported on code.google.com by Vienna...@hotmail.com on 31 Jan 2015 at 9:13

Attachments:

GoogleCodeExporter commented 8 years ago

Thanks for this bug report and the kind words that come with it.

I used the pmap tool and got a perfectly stable output, at least for the 15 
minutes I let Flowblade run:

0000000000400000   2804K r-x-- python2.7
00000000008bc000      4K r---- python2.7
00000000008bd000    468K rw--- python2.7
0000000000932000     72K rw---   [ anon ]
000000000120c000  18988K rw---   [ anon ]
00007f2730000000    132K rw---   [ anon ]
00007f2730021000  65404K -----   [ anon ]
00007f2738000000    132K rw---   [ anon ]
00007f2738021000  65404K -----   [ anon ]
00007f273fff8000  65540K rw-s- pulse-shm-1799224795
00007f2744000000    132K rw---   [ anon ]
---etc

So this issue cannot be reproduced on my system.

First I would like to find out if this is the same bug that was discussed here:

http://sourceforge.net/p/mlt/bugs/221/

This bug has been fixed in MLT. To test if this fixes your issue too, you can 
compile and install the repository version MLT.

Below is URL to page that has a script that builds and installs repository 
versions of both Flowblade and MLT into your home folder. You can remove them 
just by deleting the folder to continue using your installed version. The 
dependency list may not be up to date, but it will get you started. 

http://www.mltframework.org/bin/view/MLT/BuildScripts

Original comment by janne.li...@gmail.com on 3 Feb 2015 at 9:07

GoogleCodeExporter commented 8 years ago

Thank you very much for your feedback and help!

The MLT-bugreport describes indeed a very similar problem, Fortunately in my 
case the memory-usage was nowhere increasing so extremely rapidly (about 
60MB/s) as in the bugreport, although the result was the same - the process 
consumed all the available memory and swap. 

The buildscript for MLT and Flowblade worked fine after some small adjustments:

gerhard@paisley:~/flowblade/20150204$ ./start-flowblade
FLOWBLADE MOVIE EDITOR 0.17 repository/dev
---------------------------
Launch script dir: /home/gerhard/flowblade/20150204/flowblade-trunk
Running from filesystem...
MLT found, version: 0.9.3
...

and after almost half an hour everything, especially the memory-usage seems to 
be running "under normal conditions". I guess I can confirm now that using MLT 
0.9.3 instead of 0.9.2 has been the solution for the problem here.

Thanks again!

Original comment by Vienna...@hotmail.com on 4 Feb 2015 at 1:58

Racer-666 / flowblade

High memory usage #107