3 ms·
I wonder how many applications will start leaking memory as a result of this? Cyclic references are not that uncommon in many algorithms, and identifying the ne
by falcolas 12y ago
I wonder how many applications will start leaking memory as a result of this? Cyclic references are not that uncommon in many algorithms, and identifying the need to remove these will be challenging for applications which relied on automatic identification will take time.
- jahewson 12y agoXcode can help with that, as it says in the "Transitioning to ARC Release Notes": > To aid in migrating existing applications, the ARC migration tool in Xcode 4.3 and later supports migration of garbage collected OS X applications to ARC.
- jjoonathan 12y agoWhen it comes to overall ease of use, the importance of tooling dwarfs the importance of GC vs RC, and apple has had really solid RC tooling for a while. It graphs memory usage, searches out leaked objects (by injected GC or by diffs), lists them, lists the retain/release events with timestamps, and lets you jump to the responsible code with a single click. Compare that to the nightmare of trying to get a misbehaving GC to cooperate and suddenly it doesn't seem so crazy. EDIT: Or at least they had such tools 5-6 years ago, regression is certainly possible. For unrelated reasons I've been playing in other playgrounds for the last 5-6 years so I can't say for sure.