It's still unclear whether these are actual leaks (orphaned references), unconstrained growth, or deallocated memory whose blocks haven't been reclaimed by the OS. Automatic memory management would only help with the first case, and both Obj-C and Swift have it by default. Of course, it's entirely possible that the sources of these leaks are written in another language (C++ is fairly common) or Obj-C with ARC turned off (if that's even still allowed within Apple).