Wow. Thanks for the info. I am indeed seeing the leak on the iPad but not in
the simulator. Same with your code. I am using the newest Xcode 8.2.1 (8C1002)
Please keep me posted and I’ll do the same.
Thanks!
Chris
On Dec 20, 2016, at 2:02 AM, Ray Fix
mailto:ray...@gmail.com>> wrote:
Thanks for
Thanks for the update Chris. Hmm...
So, I get memory runtime issues if I run this on an actual device iPad Air 2
(iOS 10.2) with Version 8.2 (8C38). Can’t get it to happen on the simulator.
Can’t get it to happen if I make a macOS command line tool and inspect it with
the leaks command.
(I r
Interesting. Thanks. I’ll have to try that.
The latest Xcode 8.2 release version seems to have fixed this. I am no longer
seeing the leak.
Take care,
Chris
> On 17 Dec 2016, at 02:33, Ray Fix wrote:
>
> FWIW, seeing this too. Also, when I boiled the project down to a macOS
> command line and
FWIW, seeing this too. Also, when I boiled the project down to a macOS command
line and run the “leaks" cli I don’t see the leak. 🤔
Ray
> On Oct 14, 2016, at 9:42 AM, Chris Chirogene via swift-users
> wrote:
>
> Xcode8 is showing a memory leak in instruments and the memory graph. I have
>
Xcode8 is showing a memory leak in instruments and the memory graph. I have
narrowed it down to this: deriving from NSObject produces a leak indication. I
have no idea why.
I need an NSObject to later use the @objc directive.
The Test instance stored in the mDict Dictionary is indicated as a leak
