Sdwebimage: always crash

[supermanmwg]

sdwebImage version 4.1.2
error stack:

0 CoreGraphics | _ERROR_CGDataProvider_BufferIsNotReadable + 16
-- | --
1 CoreGraphics | CGDataProviderRetainBytePtr + 216
2 QuartzCore | CA::Render::(anonymous namespace)::create_image_from_image_data(CGImage*, CGColorSpace*, unsigned int, unsigned int, double) + 196
3 QuartzCore | CA::Render::create_image(CGImage*, CGColorSpace*, unsigned int, double) + 868
4 QuartzCore | CA::Render::copy_image(CGImage*, CGColorSpace*, unsigned int, double, double) + 472
5 QuartzCore | CA::Render::prepare_image(CGImage*, CGColorSpace*, unsigned int, double) + 20
6 QuartzCore | CA::Layer::prepare_commit(CA::Transaction*) + 420
7 QuartzCore | CA::Context::commit_transaction(CA::Transaction*) + 576
8 QuartzCore | CA::Transaction::commit() + 580
9 QuartzCore | CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) +92
10 CoreFoundation | ___CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 32
11 CoreFoundation | ___CFRunLoopDoObservers + 412
12 CoreFoundation | ___CFRunLoopRun + 1436
13 CoreFoundation | CFRunLoopRunSpecific + 552
14 GraphicsServices | GSEventRunModal + 100
15 UIKit | UIApplicationMain + 236
16 tieba | main (main.m:36)
17 libdyld.dylib | _start + 4

I think my problem as well as #2077 .
but if I set shouldDecompressImages property to false. like below:
SDWebImageDownloader.shared().shouldDecompressImages = false
SDImageCache.shared().config.shouldDecompressImages = false

what is the disadvantage to set them? load image slow or what?

[dreampiggy]

OS version ? If >= iOS 11.2, seems Apple's bug...See #2226

For what actual shouldDecompressImages & scaleDownlargeImages means, see #2273

The advantage of force decode, means we can decode the image before UIImageView actual rendering it, in the background queue. If you don't do this, Core Animation will try to decode it during rendering on the main queue and reduce the frame rate.

The disadvantage is that during the force decode process, we need another CGBitmapContext and draw images. This process will cause a temporary memory peak. But this will drop down to a lower value if the decoding process finished...Only if the image resolution is large, or the concurrent decoding images count become large, the memory peak will cause OOM. (But mostly, a 500x500 images only consume 7MB, a new CGBitmapContext may contains the same memory like this. Only if you have more than 50 images to be decoding at the same time may cause the OOM)

This is a banlance between Time & Space. For most cases we enable this feature to keep frame rate. Only if you're loading something big images, you should consider to disable this.

[supermanmwg]

thanks a lot. and it only crashed OS>11.2. I will see #2273 soon. thank again.