I was able to access object variable even after release method is called ios

Question

 Profile *myProfile= [[Profile alloc]init];

[myProfile setName:@"Jhon Applesead"];
[myProfile setCompany:@"Apple"];

[myProfile release];

NSLog(@"Name is %@", [myProfile name]);

Log is

2013-02-28 15:41:36.866 Practice[8124:303] Name is Jhon Applesead

same http://stackoverflow.com/questions/7764330/object-existing-after-release — iPatel, Feb 28 '13 at 10:22
http://stackoverflow.com/questions/6441218/can-a-local-variables-memory-be-accessed-outside-its-scope — iPatel, Feb 28 '13 at 10:23

Anil Varghese · Answer 1 · 2013-02-28T11:07:26.293

When you send a release message on an object, the object is actually not being removed from the memory. The release message simply decrements the reference count by one only. If the reference count is zero the object is marked as free. Then the system remove it from the memory. Until this deallocation happens you can access your object. Even if you release the object your object pointer still points to the object unless you are assigning nil to the pointer.

Hossam Ghareeb · Answer 2 · 2013-02-28T11:25:57.883

1

I Think that's because you didn't release name and company inside the dealloc of Profile

edited Feb 28 '13 at 11:25

answered Feb 28 '13 at 10:28

Hossam Ghareeb

7,063
3
53
64

score 1 · Answer 3 · answered Feb 28 '13 at 10:29

release does not necessarily destroy objects. It simply decrements the retain count by one. And if that retain count ever gets to zero, only then the object is deallocated. So this code works because a release happens but without triggering a dealloc.

For more details, see Apple's memory management guide.

I was able to access object variable even after release method is called ios

3 Answers3