Was just wondering if anyone's run into this as well, and if it's anything to worry about:
Asked
Active
Viewed 493 times
1 Answers
3
Obviously the session has to have a reference to the cache. The cache probably takes a delegate, and the session is that delegate. The NSURL APIs have always used a strong delegate model, so such a cycle would make sense.
I wouldn't worry about it; the retain cycle should get broken when you invalidate the session. (If it doesn't, then file a bug.)

dgatwood
- 10,129
- 1
- 28
- 49
-
I figured as much, but I'm wondering what's going on since this didn't seem to be an issue before Xcode 8 / iOS 10. Seems like there are other issues (e.g. properties of singleton classes being reported as memory leaks) with memory leak analyses. – funct7 Nov 29 '16 at 02:56
-
1I tried to resolve this issue by invalidating session but it didn't work. – Martin Jan 02 '17 at 13:07