Hi Jean,

Thank you very much for your polite and
informative email.

Both are fine qualities.

For what it's worth, I

    installed debian's libsdl2 package with
    debugging symbols,

        root$ aptitude install libsdl2-2.0-0-dbgsym

    re-ran the small test case under valgrind

        $ valgrind --track-origins=yes --leak-check=full 
--freelist-vol=100000000 --log-file=/tmp/valgrind_with_sdl_dbg.log -v kdenlive 

    counted how many times the key word "frame" occurs in valgrind's log, and

    found over a hundred.

Here's an example:

    67,108,864 bytes in 1 blocks are possibly lost in loss record 51,223 of 
       at 0x48317F4: memalign (vg_replace_malloc.c:858)
       by 0x4B8FD11: pool_fetch (mlt_pool.c:137)
       by 0x4B8FD11: mlt_pool_alloc (mlt_pool.c:292)
       by 0x18F91A44: producer_get_image (producer_pixbuf.c:718)
       by 0x4B76707: mlt_frame_get_image (mlt_frame.c:620)
       by 0x27A3DDE4: filter_get_image (filter_deinterlace.c:307)
       by 0x4B76707: mlt_frame_get_image (mlt_frame.c:620)
       by 0x1825D934: get_image (filter_fieldorder.c:33)
       by 0x4B76707: mlt_frame_get_image (mlt_frame.c:620)
       by 0x1825C1A5: filter_get_image (filter_crop.c:76)
       by 0x4B76707: mlt_frame_get_image (mlt_frame.c:620)
       by 0x18261ED7: filter_get_image (filter_rescale.c:221)
       by 0x4B76707: mlt_frame_get_image (mlt_frame.c:620)

Maybe it's just a coincidence.

I dunno.

I look forward to your next update.


> Sorry for the late feedback. So I made a few tests and found some
> interesting facts.
> The problem seems related to frame buffer.
> When setting the "buffer" property to 0 on the consumer (sdl2_audio) in
> Kdenlive, the memory usage stays stable (around 500Mb).
> When setting the buffer to 25 (default in Kdenlive), I get 2 different
> situations:
> - When using an HD 25fps profile, memory usage goes to about 700Mb
> - When using a SD NTSC profile, memory usage quickly goes up to 2.3Gb.
> These tests were done with the image attached in the latest email (3800x2500
> jpeg).
> I will try to make more tests but wondering if the frame caching bugs when
> using profile with a non integer fps profile..
> Regards
> jb
> > So,
> > Kingsley
> > 

Time is the fire in which we all burn.

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Mlt-devel mailing list

Reply via email to