Making Your Own Memory Graph To Detect Memory Issues On iOSby@davidgg
1,915 reads
1,915 reads

Making Your Own Memory Graph To Detect Memory Issues On iOS

by David Grigoryan6mApril 13th, 2021
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

Apple has shown several approaches that allow us to debug issues related to the application's memory. Xcode Memory Graph captures every application's objects and represents it into a nice and convenient graph with nodes and relations between them. Unfortunately, you can't retrieve this graph from shipped binary*, so if you have some undefined behaviour in your app you are not able to see the detailed information about your app's state. This approach has several advantages: It takes less time to build a graph than Xcode's Memory Graph implementation. It is not recommended to use these techniques in your production code.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail

Coin Mentioned

Mention Thumbnail
featured image - Making Your Own Memory Graph To Detect Memory Issues On iOS
David Grigoryan HackerNoon profile picture
David Grigoryan

David Grigoryan

@davidgg

Senior Software Engineer / iOS Developer

About @davidgg
LEARN MORE ABOUT @DAVIDGG'S
EXPERTISE AND PLACE ON THE INTERNET.

Share Your Thoughts

About Author

David Grigoryan HackerNoon profile picture
David Grigoryan@davidgg
Senior Software Engineer / iOS Developer

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
L O A D I N G
. . . comments & more!