Home/ Questions/Q 1048943
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T16:32:12+00:00

SO I already know about memory management in objective C, and I never had

  • 0

SO I already know about memory management in objective C, and I never had to know about it while programming in .net (C#). But i still have some questions about how everything is done.

-Why does the code leak in objective c if we allocate an object and not release it?

-Why doesn’t this leak in C#?

-What are some advantages and disadvantages of automatic-garbage-collecting?

-Why not use autorelease on every allocated object (Objective C)?

-Is it possible to take care of the memory manually (C#)? so let’s say i instantiate an object, and when I’m done i want to release it, and i don’t want to wait for the garbage collector to do it?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    • It leaks in Objective-C because Objective-C doesn’t take any action on it. It relies on you doing all the work. It doesn’t leak in C# (more precisely, in .NET) because it employs a garbage collector which cleans up objects that are no longer used.

    • The main advantage of garbage collection is the above: you have far fewer memory leaks. (It’s still possible to have a memory leak, e.g. by filling a list indefinitely, but that’s harder to do accidentally.) It used to be thought that garbage collection has a disadvantage in that it could slow down the program because it keeps doing the garbage collection in the background and you have little control over it. In reality, however, the difference is negligible: there are other background tasks on your computer (e.g. device drivers) running all the time, the garbage collector doesn’t break the camel’s back either.

    • Auto-deallocation (as it is employed in C++ when a non-pointer variable goes out of scope) is dangerous because it opens the possibility to have a reference to it still in existence even after the object has been disposed. If your code then tries to access the object, the process goes kaboom big time.

    • Yes, it is possible to tell C# to release memory by invoking the garbage collector directly (GC.Collect()). However, I have yet to see a case where this is at all necessary. If you actually run out of memory, the garbage collector will already kick in automatically and free as much as it can.

    • 0