为什么会出现“潜在泄漏”?

时间:2015-06-29 08:08:04

标签: ios objective-c memory-management core-graphics

Xcode的分析仪抱怨“存在潜在的物体泄漏”。突出显示以下方法中的第一行:

- (void)retrieveBeginRestoreData {
    self.restoreContext = [self.image newARGBBitmapContext];
    if (!self.restoreContext) self.restoreData = nil;
    CGRect rect = {{0,0},self.image.size};

    CGContextDrawImage(self.restoreContext, rect, self.image.CGImage);
    self.restoreData = CGBitmapContextGetData(self.restoreContext);
}

我有一个声明的属性:

@property (nonatomic, assign) CGContextRef restoreContext

newARGBBitmapContext由以下内容定义:

- (CGContextRef)newARGBBitmapContext {
    CGContextRef    context = NULL;
    CGColorSpaceRef colorSpace;
    void *          bitmapData;
    size_t             bitmapByteCount;
    size_t             bitmapBytesPerRow;

    // Get image width, height. We'll use the entire image.
    size_t pixelsWide = CGImageGetWidth(self.CGImage);
    size_t pixelsHigh = CGImageGetHeight(self.CGImage);

    // Declare the number of bytes per row. Each pixel in the bitmap in this
    // example is represented by 4 bytes; 8 bits each of red, green, blue, and
    // alpha.
    bitmapBytesPerRow   = (pixelsWide * 4);
    bitmapByteCount     = (bitmapBytesPerRow * pixelsHigh);

    // Use the generic RGB color space.
    //    colorSpace = CGColorSpaceCreateWithName(kCGColorSpaceGenericRGB);
    colorSpace = CGColorSpaceCreateDeviceRGB();
    if (colorSpace == NULL)
    {
        fprintf(stderr, "Error allocating color space\n");
        return NULL;
    }

    // Allocate memory for image data. This is the destination in memory
    // where any drawing to the bitmap context will be rendered.
    bitmapData = malloc( bitmapByteCount );
    if (bitmapData == NULL)
    {
        fprintf (stderr, "Memory not allocated!");
        CGColorSpaceRelease( colorSpace );
        return NULL;
    }

    // Create the bitmap context. We want pre-multiplied ARGB, 8-bits
    // per component. Regardless of what the source image format is
    // (CMYK, Grayscale, and so on) it will be converted over to the format
    // specified here by CGBitmapContextCreate.
    context = CGBitmapContextCreate (bitmapData,
                                     pixelsWide,
                                     pixelsHigh,
                                     8,      // bits per component
                                     bitmapBytesPerRow,
                                     colorSpace,
                                     (CGBitmapInfo)kCGImageAlphaPremultipliedFirst);
    if (context == NULL)
    {
        free (bitmapData);
        fprintf (stderr, "Context not created!");
    }

    // Make sure and release colorspace before returning
    CGColorSpaceRelease( colorSpace );

    return context;
}

我设法解决了这个问题,而是将restoreContext声明为头文件中的实例变量; “潜在泄漏”警告消失了。

问题:

  • 首先是什么问题?
  • 当我停止将restoreContext声明为属性时,问题是如何解决的?
  • 解决restoreContext被声明为属性的问题的正确方法是什么?

1 个答案:

答案 0 :(得分:1)

这一行

self.restoreContext = [self.image newARGBBitmapContext];

执行以下操作:

  1. 它(可能)创建CGContext

  2. 的实例对象
  3. 由于方法名称以new开头,因此会应用所有权转移。这意味着接收者(您的代码)负责释放它。

  4. 当第二次运行代码行时,将覆盖现有CGContext实例的引用而不释放实例,它指向。旧实例将泄漏。