Memory Leaks In iOS

Updated 31 August 2021


Memory leaks in iOS occurs when the allocated amount of memory can not be deallocate due to retain cycles.

Swift uses the Automatic Reference Counting to manage the memory leaks.

Memory leaks increase the memory footprint incrementally in the app.

Memory leaks cause a crash in the application.

In the general way memory leaks occur when two objects strongly hold the reference to each other.

ARC maintains the reference count when any variable deallocate the memory the reference count will 0.

Memory leaks make the application heavy and slow.

Memory leaks may occurs due to third-party SDK, framework, and wrong variable declaration.

Automatic Refrence Counting

Swift uses Automatic Reference Counting (ARC) to track and manage your app’s memory usage. In most cases,

this means that memory management “just works” in Swift, and you don’t need to think about memory

management yourself.

Arc works when you create any instance of the class and some memory occupied by Arc to store the information.

And when the instance is no longer needed then the ARC deallocates the memory and sets the reference count 0.

Example of memory leak

We will generate the memory leaks using two dependent strong objects.

Taking two classes and both contain the instance of each other with a strong reference.

In WebkulServer class have webkulClient object with strong refrence.

And in WebkulClient class have a WebkulServer object with strong reference.

Both object never releases the memory because both never be nil.

And both will create the cycle which will call the memory leaks.

So for avoiding memory leaks we need to use one object a weak or unowned.

Below in screenshots, the red color cross icon shows the leaks.


A weak` reference does not increase the retain count. a weak reference does not take ownership of an object.


The unowned reference does not increase the retain count. And unowned reference never be nil.

Now we used weak with WebkulClient and then no retain cycle will create with dependent objects.

To check the memory leaks use profiling and then you can get the leaks information.

Now after using the weak there are no leaks.

And thanks for reading this blog, for detail info please click here

For more blogs please click here.

So pls follow the above step and And if you have any issues or suggestions you can leave your message in the comment section I will try to solve this.

. . .

Leave a Comment

Your email address will not be published. Required fields are marked*

Be the first to comment.

Start a Project

    Message Sent!

    If you have more details or questions, you can reply to the received confirmation email.

    Back to Home