We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In CGImage here, we specify OnDemand caching for images loaded from WIC frame decoders.
OnDemand
Unfortunately, if you do this:
CFDataRef data = CFDataCreate(...); CGImageRef image = CGImageCreateWithDataProvider(CGDataProviderCreateWithCFData(data), ...); CFRelease(data); CGImageDoAnythingAtAll(image);
Line 4 will cause CGImage through WIC to read the buffer backing the CGData destroyed on line 3.
Interim solution: Switch to OnLoad.
OnLoad
Suggested future solution: Implement an IWICStream that is backed by a CGDataProvider.
The text was updated successfully, but these errors were encountered:
As part of the aforementioned future solution, we could switch back to OnDemand (and reap all the savings.)
Sorry, something went wrong.
Saw this issue when we did bitmap context, made these changes in bitmap context. missed the decoder one. Updating
Definitely don't do it tonight! I've worked around it for CoreGraphics.Drawing.UnitTests.
LOL so the existing CGImage tests would of got this easily, but we autoreleased the CFData, rather than a release right away.
#1413
msft-Jeyaram
No branches or pull requests
In CGImage here, we specify
OnDemand
caching for images loaded from WIC frame decoders.Unfortunately, if you do this:
Line 4 will cause CGImage through WIC to read the buffer backing the CGData destroyed on line 3.
Interim solution: Switch to
OnLoad
.Suggested future solution: Implement an IWICStream that is backed by a CGDataProvider.
The text was updated successfully, but these errors were encountered: