Skip to content
This repository

runningOperations cause #301

Closed
jklimke opened this Issue · 0 comments

2 participants

jklimke Olivier Poitrey
jklimke

When downloading images asynchronously, there are cases, where there are conflicting accesses to runningOperations of SDWebImageManager that are not synchronized. So it happens, that errors like this one appear:

'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 1 beyond bounds [0 .. 0]'`

I propose to synchronize at least modifying access to the job queue. Or is there already a synchronization that i missed to use ?

Olivier Poitrey rs closed this in b27d571
Martín Conte Mac Donell Reflejo referenced this issue from a commit in Kicksend/SDWebImage
Martín Conte Mac Donell Reflejo Merge remote-tracking branch 'upstream/master'
* upstream/master:
  Prefetching file properties in the disk cleaning enumerator
  correct cachePolicy constants.
  Add (kinda) LIFO queue mode support for image downloading (fix #294)
  Add completion block support to `SDWebImagePrefetcher` (fix #127)
  Add `SDWebImageManager` delegate allowing fine control of manager's cache-in
  Add ability to set custom downloader HTTP headers (fix #171)
  Synchronize access to SDWebImageManager's mutable structures (fix #301)
  [BUG] Fix invalid alpha on JPEG files
f62788f
Martín Conte Mac Donell Reflejo referenced this issue from a commit in Kicksend/SDWebImage
Martín Conte Mac Donell Reflejo Merge remote-tracking branch 'upstream/master'
* upstream/master:
  Detect parent operation cancellation in download operation completion block
  Prefetching file properties in the disk cleaning enumerator
  correct cachePolicy constants.
  Add (kinda) LIFO queue mode support for image downloading (fix #294)
  Add completion block support to `SDWebImagePrefetcher` (fix #127)
  Add `SDWebImageManager` delegate allowing fine control of manager's cache-in
  Add ability to set custom downloader HTTP headers (fix #171)
  Synchronize access to SDWebImageManager's mutable structures (fix #301)
  [BUG] Fix invalid alpha on JPEG files
1f88283
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.