[Ffmpeg-devel] Memory leakage when using libavcodec with ffmpeg2theora

Viktor Kompaneyets vato
Thu May 12 20:29:00 CEST 2005


? ????????? ?? ???????, 12-???-2005 21:11 M?ns Rullg?rd ???????(a):
> Viktor Kompaneyets <vato at wnet.ua> writes:
> > ==9134== LEAK SUMMARY:
> > ==9134==    definitely lost: 0 bytes in 0 blocks.
> > ==9134==      possibly lost: 0 bytes in 0 blocks.
> > ==9134==    still reachable: 65552 bytes in 2 blocks.
>
> This doesn't necessarily mean it's a leak.
>
> > ==9134==         suppressed: 0 bytes in 0 blocks.
> > ==9134== Reachable blocks (those to which a pointer was found) are not
> > shown. ==9134== To see them, rerun with: --show-reachable=yes
>
> Could you please rerun with --show-reachable=yes?

I'll do it tomorrow, but this is situation, in which valgrind don't help - the 
programs ran out of memory (even swap) after a couple days of encoding. But, 
if we stops them - the heap is freed! So only hard leaks we can see. 

-- 
Viktor Kompaneyets
Wnet ISP





More information about the ffmpeg-devel mailing list