如何不使用SoftwareRenderer创建CIContext渲染CIFilter避免内存泄漏

Hey there! I see you're trying to use a hardware-accelerated CIContext (by disabling the software renderer) to avoid memory leaks, and you want to apply it to CIFilter processing—since the existing info you found only covers scaling scenarios. Let's fix up your code and walk through the key points step by step.

First, let's address a few issues in your sample code, then share the corrected version:

Key Issues in Your Current Code #

• Variable inconsistency: You assign the context to weakSelf.context but try to use weakSelf.myCIContext later—this is a typo that will cause crashes or unexpected behavior.
• Unreleased CGImage: createCGImage: returns a Core Foundation object (CGImageRef), which ARC doesn't automatically manage. Failing to release it will lead to memory leaks.
• CIContext creation overhead: Creating a CIContext every time you process an image is inefficient (it's a heavyweight object). You should reuse a single instance instead of recreating it in each @autoreleasepool.
• Incorrect render rect: When creating the CGImage, you use the original image's extent instead of the cropped image's extent—this can lead to incorrect rendering bounds.

Corrected Implementation #

First, add a CIContext property to your class (so we can reuse it):

@property (nonatomic, strong) CIContext *hardwareCIContext;

Initialize it once (e.g., in viewDidLoad or your class's init method):

// Initialize hardware-accelerated CIContext once (reuse this instance)
self.hardwareCIContext = [CIContext contextWithOptions:@{kCIContextUseSoftwareRenderer: @NO}];

Then, use this reused context for your filter processing:

__weak typeof(self) weakSelf = self;
@autoreleasepool {
    if (!weakSelf) return;
    
    // Create and configure the comic effect filter
    CIFilter *comicFilter = [CIFilter filterWithName:@"CIComicEffect" withInputParameters:@{@"inputImage": weakSelf.myCIImage}];
    CIImage *resultImage = comicFilter.outputImage;
    
    // Crop the filtered result to your desired size
    CGRect cropRect = CGRectMake(0, 0, weakSelf.affineClampImage.size.width * scale, weakSelf.affineClampImage.size.height * scale);
    CIImage *croppedImage = [resultImage imageByCroppingToRect:cropRect];
    
    // Render the cropped image using our hardware-accelerated CIContext
    CGImageRef cgImage = [weakSelf.hardwareCIContext createCGImage:croppedImage fromRect:croppedImage.extent];
    
    if (cgImage) {
        UIImage *renderedImage = [UIImage imageWithCGImage:cgImage];
        // Use your rendered image here (e.g., assign to an image view)
        weakSelf.targetImageView.image = renderedImage;
        
        // Mandatory: Release the CGImage to avoid memory leaks (ARC doesn't manage Core Foundation objects)
        CFRelease(cgImage);
    }
}

Critical Notes #

• Reuse CIContext: Creating a new CIContext for every image operation is costly and can contribute to memory bloat. Reusing a single instance is best practice for both performance and memory management.
• Release CGImageRef: Always call CFRelease on the CGImageRef returned by createCGImage:fromRect:—this is non-negotiable to prevent memory leaks, as ARC doesn't handle Core Foundation objects.
• Weakself checks: Adding a quick if (!weakSelf) check ensures you don't try to access a deallocated object, which is a good safeguard.
• Hardware compatibility: The hardware-accelerated context uses the GPU, so make sure your filter operations are GPU-compatible (most standard Apple CIFilters work fine, but some custom filters might not).

内容的提问来源于stack exchange，提问作者Reza.Ab