Recherche avancée

Sur d’autres sites (9544)

• lavf/flvdec : replace a private option with a field in FFFormatContext

  13 octobre 2024, par Anton Khirnov

  lavf/flvdec : replace a private option with a field in FFFormatContext
  The demuxer's 'missing_streams' private option is used to communicate
  
  information from the demuxer to avformat_find_stream_info(). However,
  
  that is not only unnecessarily complicated, it also leaks internal
  
  information to users, e.g. this option appears in the results of the
  
  fate-flv-demux test.
  Use a new field in FFFormatContext to communicate this information
  
  instead.
  

  • [DH] libavformat/demux.c
  • [DH] libavformat/flvdec.c
  • [DH] libavformat/internal.h
  • [DH] tests/ref/fate/flv-demux

• avformat/matroskaenc : Remove allocations for Attachments

  29 décembre 2019, par Andreas Rheinhardt

  avformat/matroskaenc : Remove allocations for Attachments
  If there are Attachments to write, the Matroska muxer currently
  
  allocates two objects : An array that contains an entry for each
  
  AttachedFile containing just the stream index of the corresponding
  
  stream and the FileUID used for this AttachedFile ; and a structure with
  
  a pointer to said array and a counter for said array. These uids are
  
  generated via code special to Attachments : It uses an AVLFG in the
  
  normal and a sha of the attachment data in the bitexact case. (Said sha
  
  requires an allocation, too.)
  But now that an uid is generated for each stream in mkv_init(), there is
  
  no need any more to use special code for generating the FileUIDs of
  
  AttachedFiles : One can simply use the uid already generated for the
  
  corresponding stream. And this makes the whole allocations of the
  
  structures for AttachedFiles as well as the structures itself superfluous.
  
  They have been removed.
  In case AVFMT_FLAG_BITEXACT is set, the uids will be different from the
  
  old ones which is the reason why the FATE-test lavf-mkv_attachment
  
  needed to be updated. The old method had the drawback that two
  
  AttachedFiles with the same data would have the same FileUID.
  
  The new one doesn't.
  Also notice that the dynamic buffer used to write the Attachments leaks
  
  if an error happens when writing the buffer. By removing the
  
  allocations potential sources of errors have been removed.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/matroskaenc.c
  • [DH] tests/ref/lavf/mkv_attachment

• memory leak in ffmpeg

  28 janvier 2016, par Jerry Dubuke

  I have incorporated ffmpeg into an iPad app, and when I stream via rtsp, I see the app crash after a few hours of streaming.

  When i debug the app via Instruments/leaks, i found the offending leak is inside an FFMPEG library, and the offending function is av_buffer_realloc.

  Does anyone know how I can proceed with getting this leak addressed/fixed ? I do not have a lot of tools at my disposal, and I am not even sure where to post to get this problem addressed ?

  Thank you for any help/suggestions.

  as per a request, here is code. BUT, it has nothing to do with MY code, as the streaming is occurring, there is a leak in FFMPEG. Whether I set my timer to 1/30 sec, or 1/60 second, the leak is consistent, and as stated above is in a routine that is not mine - it is in the ffmpeg library.

  video = [[RTSPPlayer alloc] initWithVideo:szURL usesTcp:NO];
  
  lastFrameTime = -1;
  
  // seek to 0.0 seconds
  
  [video seekTime:0.0];
  
  [_nextFrameTimer invalidate];
  
  self.nextFrameTimer = [NSTimer scheduledTimerWithTimeInterval:1.0/30 target:self selector:@selector(displayNextFrame:) userInfo:nil repeats:YES];

  here is displayNextFrame. It calls into RSTPPlayer to get a snapshot video frame :

  {
  
      if (![video stepFrame]) {
  
          [timer invalidate];
  
          [video closeAudio];
  
          return;
  
      }
  
      self.theImageView.image = video.currentImage;
  
  }

  Here is the currentImage code from RTSPPlayer :

  - (UIImage *)currentImage
  
  {
  
      if (!pFrame->data[0]) return nil;
  
      [self convertFrameToRGB];
  
      return [self imageFromAVPicture:picture width:outputWidth height:outputHeight];
  
  }

  Here is imageFromAVPicture :

  - (UIImage *)imageFromAVPicture:(AVPicture)pict width:(int)width height:(int)height
  
  {
  
      CGBitmapInfo bitmapInfo = kCGBitmapByteOrderDefault;
  
      CFDataRef data = CFDataCreateWithBytesNoCopy(kCFAllocatorDefault, pict.data[0], pict.linesize[0]*height,kCFAllocatorNull);
  
      CGDataProviderRef provider = CGDataProviderCreateWithCFData(data);
  
      CGColorSpaceRef colorSpace = CGColorSpaceCreateDeviceRGB();
  
      CGImageRef cgImage = CGImageCreate(width, 
  
                                         height, 
  
                                         8, 
  
                                         24, 
  
                                         pict.linesize[0], 
  
                                         colorSpace, 
  
                                         bitmapInfo, 
  
                                     provider, 
  
                                     NULL, 
  
                                     NO, 
  
                                     kCGRenderingIntentDefault);
  
  CGColorSpaceRelease(colorSpace);
  
  UIImage *image = [UIImage imageWithCGImage:cgImage];
  
  
  
  CGImageRelease(cgImage);
  
  CGDataProviderRelease(provider);
  
  CFRelease(data);
  
  
  
  return image;

  }

  Thank you for any assistance.