Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upPotential Leaks in Xcode 7 when using static Analyzer #116
Conversation
jcarroll3
commented
Oct 9, 2015
|
The property, which is set in the init is assign. If you auto release its highly likely you'll get a zombie. I think this alteration will fix the SA error and maintain functionality. #118 |
arvchz
commented
Jun 2, 2016
|
Any updates on this ? |
3a4oT
commented
Aug 3, 2016
|
Hey is there some person who have permission to merge?? |
|
The problem here is it doesn't account for the On line 175 which takes care of freeing the |
valerieosmith
commented
Jan 26, 2018
|
It's true that the SA doesn't account for the CFRelease in the dealloc, so there is no actual leak. But this silences the SA and also makes ownership of the object clear: #165 |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

tringkishorekumar commentedSep 29, 2015
We are getting Potential Leaks in Reachability.m
Leaks showing in methods "reachabilityWithHostname:" and "reachabilityWithAddress:".
Line numbers 101 and 114 in Reachability.m, "Potential leak of an object stored into 'ref'"
Attached the screenshot of the issue.