Xcode settings-app memory burst

When you find out what is not written in your project, just start the app memory to soar to 50M or even more than 60M, then please look down, this article is absolutely very useful to you!

1. Enable Zombie Object:

In order to facilitate our debugging procedures, we will generally check the first item. In this case, in our program when the wild pointer is called, when you hit the global breakpoint, the program will be positioned in the specific crash location, for our debugging to bring great convenience;

(Here, please do not ask me how to set a global breakpoint ...??) ）

It should be noted that in our packaging program upload, we have to remove this tick, the specific reason to take me to translate the developer documentation, to supplement the authority of the reason! TODO-------

2.Enable Address Sanitizer:

If the symptoms of your program are the same as described above, then you can check if this item was accidentally checked by you. Please uncheck, in run once, see the results after your mood is not all of a sudden easy, originally you can write the memory so small project! Here's a specific reason: Address sanitizer is a great technology that can help us find a lot of problems in C code. It's not perfect, it can't find all the errors, but it can still provide very useful diagnostic information. Here, I strongly recommend that you try to use it in your own code, and you will find the result that surprises you.

Detailed analysis: Immediately after work, I will not wordy! For details, please click

Xcode settings-app memory burst