Recherche avancée

Sur d’autres sites (10048)

• Correctly Allocate And Fill Frame In FFmpeg

  24 février 2016, par mFeinstein

  I am filling a Frame with a BGR image for encoding, and I am getting a memory leak. I think I got to the source of the problem but it appears to be a library issue instead. Since FFmpeg is such a mature library, I think I am misusing it and I would like to be instructed on how to do it correctly.

  I am allocating a Frame using :

  AVFrame *bgrFrame = av_frame_alloc();

  And later I allocate the image in the Frame using :

  av_image_alloc(bgrFrame->data, bgrFrame->linesize, bgrFrame->width, bgrFrame->height, AV_PIX_FMT_BGR24, 32);

  Then I fill the image allocated using :

  av_image_fill_pointers(bgrFrame->data, AV_PIX_FMT_BGR24, bgrFrame->height, originalBGRImage.data, bgrFrame->linesize);

  Where originalBGRImage is an OpenCV Mat.

  And this has a memory leak, apparently, av_image_alloc() allocates memory, and av_image_fill_pointers() also allocates memory, on the same pointers (I can see bgrFrame->data[0] changing between calls).

  If I call

  av_freep(&bgrFrame->data[0]);

  After av_image_alloc(), it’s fine, but if I call it after av_image_fill_pointers(), the program crashes, even though bgrFrame->data[0] is not NULL, which I find very curious.

  Looking FFmpeg’s av_image_alloc() source code, I see it calls av_image_fill_pointers() twice inside it, once allocating a buffer buff....and later in av_image_fill_pointers() source code, data[0] is substituted by the image pointer, which is (I think) the source of the memory leak, since data[0] was holding buf from the previous av_image_alloc() call.

  So this brings the final question : What’s the correct way of filling a frame with an image ?.

• Correctly Allocate And Fill Frame In FFmpeg

  14 avril 2022, par Michel Feinstein

  I am filling a Frame with a BGR image for encoding, and I am getting a memory leak. I think I got to the source of the problem but it appears to be a library issue instead. Since FFmpeg is such a mature library, I think I am misusing it and I would like to be instructed on how to do it correctly.

  



  I am allocating a Frame using :

  



  AVFrame *bgrFrame = av_frame_alloc();


  



  And later I allocate the image in the Frame using :

  



  av_image_alloc(bgrFrame->data, bgrFrame->linesize, bgrFrame->width, bgrFrame->height, AV_PIX_FMT_BGR24, 32);


  



  Then I fill the image allocated using :

  



  av_image_fill_pointers(bgrFrame->data, AV_PIX_FMT_BGR24, bgrFrame->height, originalBGRImage.data, bgrFrame->linesize);


  



  Where originalBGRImage is an OpenCV Mat.

  



  And this has a memory leak, apparently, av_image_alloc() allocates memory, and av_image_fill_pointers() also allocates memory, on the same pointers (I can see bgrFrame->data[0] changing between calls).

  



  If I call

  



  av_freep(&bgrFrame->data[0]);


  



  After av_image_alloc(), it's fine, but if I call it after av_image_fill_pointers(), the program crashes, even though bgrFrame->data[0] is not NULL, which I find very curious.

  



  Looking FFmpeg's av_image_alloc() source code, I see it calls av_image_fill_pointers() twice inside it, once allocating a buffer buff....and later in av_image_fill_pointers() source code, data[0] is substituted by the image pointer, which is (I think) the source of the memory leak, since data[0] was holding buf from the previous av_image_alloc() call.

  



  So this brings the final question : What's the correct way of filling a frame with an image ?.

  


• ffmpeg : playing media files does not release processor after media ends ?

  2 septembre 2017, par Blake Senftner

  I have a commercial C++ application which uses FFMPEG’s libav series of dlls to play media in a Windows application. I basically started with the dranger tutorial about two years ago, and created a library that can playback USB cameras, IP camera / online streams, and media files on disk. (http://dranger.com/ffmpeg/)

  My question is directed at anyone who has created their own similar library :

  I recently noticed after playing a video file from disk (as opposed to a live stream from USB or IP source), my 8 core i7 workstation will show 28-29% CPU usage after a media file has ended. My application can play an unlimited number of videos, and each "virtual video panel" (not a window, just a "virtual tab" created using wxWidgets that holds an OpenGL context that I use to glDrawPixels() to the visible app panel) will play any of the three media types fine (USB, IP stream or media file) and when I stop a USB or IP stream my application’s CPU usage drops to zero. But when I "stop" a media file playing or the media file ends on its own the CPU usage does not drop - until the application quits.

  Three media files playing will take my application to 80-83% CPU, and it never drops. UNLESS I reuse that same "virtual video panel" to play a USB or IP stream. If I stop those streams, CPU usage is released.

  MP4 (h264) video files exhibit this "holding a processor" problem.

  MP4 (mpeg2) files do not.

  MP4 (h265) files do not.

  MPG (mpeg1) files do not.

  ASF (MS MPEG-4 Video v3) files do not.

  MKV (vp8) files do not.

  MOV files using h265 do not, as well as MOV (h264) files do not.

  FLV (sorensen) files do not, as well as FLV (h264) files do not.

  So it is not just the h264 codec.

  Anyone know what is going on, and how I tell libav to release CPU usage when a media file is no longer playing ?