Home/ Questions/Q 718125
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T05:29:27+00:00

I have some code which I think has extra release statements. Is the code

  • 0

I have some code which I think has extra release statements.

  1. Is the code incorrect?
  2. What is the end result?

I don’t understand memory management well yet – even after reading lots of articles and stackoverflow answers. Thanks for straightening me out.

Update: The attached snippet works fine, but other code has the over-release problem

NSMutableArray *points = [NSMutableArray new];
for (Segment *s in currentWorkout.segments) {
 [points addObjectsFromArray:[s.track locationPoints]];
}
[routeMap update:points];
[points release];
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No messages can safely be sent to a deallocated object. Once an object has been released a sufficient number of times, it’s deallocated. Any further messages sent to that object are going to an object that isn’t there anymore. The precise result isn’t completely predictable, but it usually ends in a crash. If you’re less lucky, it could end in much stranger ways — for example, you could theoretically wind up with an Object A getting dealloced early and Object B allocated in the same memory location, then Object B receiving messages meant for Object A that Object B does understand but isn’t supposed to receive at that time.

    Basically, follow the rules. Think of it in terms of ownership. If you’ve claimed ownership, you need to release that ownership. If you don’t own the object, you must not release it.

    • 0