will be helpful for those in need What is probably happening is that there are a few strong references to Views/iVars/Properties still left dangling when you release your infinite level view controller (by dismissing/removing from superview). Try to release all your properties and instance variables just before you release your view controller. You could also try to define all your IBOutlets (which don't get removed from the view) as Weak type, so they get released when the view controller is dismissed. Some points you can remember as a checklist for memory management:
Memory usage of program increasing over time, but memory leak tools report no issues
will help you You are most likely suffering from memory fragmentation. What happens is that as you release chunks of memory, you get little holes which might not be able to be used next time you request memory. As you continue allocating and releasing in a pattern that creates small unusable holes, the only solution is to get more hunks of memory from the system.
wish of those help Firstly, I want to give credit to @totiG for pointing out that the problem could be with the navigation controller, and he was right. There are other smaller memory issues, but the biggest by far had to do with my navigation. I kept pushing controllers onto the navigation stack, without popping them.
it fixes the issue Your segmentation fault error could stem from free(s)s in both add_user(...) and connect_user(...) functions since char s[...] is variable sized arrays on the stack, not allotted to the heap to be freed. You need to get rid of them. In the server and client sides, you don't wait your child process by using wait(..) or waitpid(..)