Behavior changes - The default query image size now changed to PHImageManagerMaximumSize #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is because the previous version use
SDWebImagePhotosPixelSize
, which may return a larger size beyond system RAM limit.For Example, if you use
SDWebImagePhotosPixelSize
to query an iPhone 5K Deep Depth Photo, iOS will return nearly 8000x8000 pixels, cause a high rate of OOM.Use
PHImageManagerMaximumSize
, can only return you nearly 4000x4000 pixels, suitable for current iPhone's display.This change is noticable, but it's suitable for most of common cases, we still query the as large as possible to original image by default. Only try to workaround with that OOM issue.