This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Memory problems

Tags: None
(comma "," separated)
orbspider
Registered Member
Posts
53
Karma
0

Re: Memory problems

Wed Aug 22, 2012 2:15 pm
My renders are often getting up to 95% ram use! If they finish about there then they make it. I'm not sure if the ram use stops increasing there but I had a 13min h264 render that failed at 96% ram use.

so, right now, I make sure my h264 are shorter than 7 or 8 min, which is fine for mp4 video.. but vob needs to be longer so it doesn't halt on the dvd while playing, so I just make the short vob's and concatenate them afterwards (with an easy Thunar right click custom action actually: cat > NEW.vob %F that joins the selected files)

my h264 renders are hitting 450mb @12Mbit/s (master copy later put thru handbrake)

I normally get ram back by restarting kdenlive, but now a few times that hasn't been enough, and I have to log-out.

and I need to get ram back down to 200mb mark to make renders. But rendering from scripts is vital to success, with no project loaded, and sometimes exiting other app's, especially chrome!

sure hope this bug will be fixed.
normcross
Registered Member
Posts
300
Karma
0

Re: Memory problems

Wed Aug 22, 2012 4:25 pm
Using the latest sunab ppa, I did a little test.

I rendered a 1080 HD project which was using 39 clips and lasted 3mins 25secs.

Memory used after boot :- 419 MiB
Load Kdenlive:- 570 MiB
Load Project:- 794 MiB
Rendering peeked at :- 2.0 GiB

So that's about 1.2 GiB to render 3min 25secs. The trouble is, I can't remember what it used to use because I never had to worry before.
orbspider
Registered Member
Posts
53
Karma
0

Re: Memory problems

Fri Aug 24, 2012 3:26 am
I switched back to rendering to mpeg2 10Mbits and it's saving me a lot of time and also melt isn't hitting the RAM ceiling

my start up ram use is between 190-220mb! lxde :)

btw, concatenating the vob's gave problems in bombono, like the new vob was shown as length of one of the concat'd vobs.. also can't generate dvd

User avatar
hvdwolf
Registered Member
Posts
60
Karma
1
OS

Re: Memory problems

Sat Aug 25, 2012 12:04 pm
Normcross said:
"So that's about 1.2 GiB to render 3min 25secs. The trouble is, I can't remember what it used to use because I never had to worry before."

What if you uninstall the 0.9.2 (or 0.9.3 sunab ppa), temporarily remove/deactivate the sunab ppas, and reinstall the stable 0.8.x version from your Ubuntu and rerun the same project (if it is compatible). What memory consumption do you get with that version?

- EDIT: and another thing: Do you use multiple threads?
I have a quad-core i7 with a possibility for 8 threads. So I use 2 threads for proxies and 3-5 threads for encoding (experimenting a little) as this really speeds up things.
Encoding h264 (mpeg4 AVC) uses (much) more memory (and processing power) then mpeg-4 ASP or mepg-2. I can imagine that when using multiple threads for encoding h264 the memory consumption will increase with equal amounts compared to mpeg4 ASP or mpeg-2. I haven't checked b.t.w.
cryophallion
Registered Member
Posts
35
Karma
0

Re: Memory problems

Thu Sep 06, 2012 6:03 pm
Some new info. So, I tried rendering my 1080i video again with the new version down to a vob. Sadly, memory leak still happens all too soon. But then I tried the bluray profile posted on another thread. That one never got above 30%, (it did use more cpu though). While the video didn't render the audio properly, which I am checking on (too slowly, as it is over two hours, and it takes 5 hours to render on my laptop), it;s interesting that it may be a melt issue within a certain profile.


DiveO
Registered Member
Posts
182
Karma
0

Re: Memory problems

Thu Sep 06, 2012 6:09 pm
Sorry to ask: but what amount of "memory" are you measuring exactly? With a virtual memory manager in place on the os side and many things going on behind the scene I always found it to be rather difficult in my system architect career so far to measure memory consumption on standard operating systems ... the only things were I could reasonable measurements are certain embedded system with fixed memory mapping and a single process/multithread setup, where everything is clear and mapped only once.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]