Détection des fuites mémoire avec Instruments
Utilisez Instruments dans Xcode pour identifier et résoudre les fuites mémoire, les cycles de rétention et les autres goulots d'étranglement liés aux performances mémoire
Détection des fuites mémoire avec Instruments est une leçon Objective-C iOS Development for Legacy & Enterprise Apps gratuite sur CoddyKit. Ceci est la leçon 1 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Objective-C iOS Development for Legacy & Enterprise Apps, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Objective-C iOS Development for Legacy & Enterprise Apps comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
What are Memory Leaks?
In Objective-C, a memory leak occurs when your app allocates memory for an object, but then loses all references to that object without deallocating it.
This means the memory is still occupied, but your app can no longer access or free it. Over time, leaks can slow down your app and even cause it to crash.
Introducing Xcode Instruments
Xcode Instruments is a powerful profiling and analysis tool provided by Apple. It helps developers understand the performance of their apps in various areas, including CPU usage, energy consumption, and crucially, memory management.
It's like an X-ray vision for your app's internals!
The 'Leaks' Instrument
Among its many templates, Instruments offers a dedicated 'Leaks' instrument. This tool is specifically designed to detect and visualize memory leaks in your Objective-C applications.
It monitors memory allocations and deallocations, highlighting objects that are still in memory but have become unreachable.
Profiling Your App for Leaks
To start detecting leaks, follow these steps:
- 1. In Xcode, go to Product > Profile.
- 2. Xcode will launch Instruments. Select the 'Leaks' template.
- 3. Click the 'Choose' button.
- 4. In Instruments, click the 'Record' button (red circle) to start running your app.
Now, interact with your app to try and trigger potential leaks.
Interpreting the Leaks Graph
As your app runs, Instruments will display a timeline graph. Look for red bars appearing in the 'Leaks' track – these indicate that a memory leak has been detected at that point in time.
The height of the bar often correlates with the amount of leaked memory or the number of leaked objects.
Pinpointing the Leak Source
To find out where a leak is happening:
- 1. Select a red bar (leak spike) in the timeline.
- 2. In the detail pane below, switch to the 'Call Tree' view.
- 3. Look for method calls highlighted in red or purple. These often point to the code responsible for allocating the leaked object.
The call stack helps you trace back to the exact line of code!
Common Cause: Retain Cycles
A very common cause of memory leaks in Objective-C (especially with ARC) is a retain cycle (also known as a strong reference cycle).
This occurs when two or more objects hold strong references to each other, forming a closed loop. Because each object thinks another object still needs it, none of them can be deallocated, even if they are no longer needed by the rest of the application.
Example: A Retain Cycle
Here's a simplified example of two classes, MyObject and OtherObject, creating a retain cycle. Notice both properties are strong.
Run this code. You'll see 'initialized' messages but no 'deallocated' messages, indicating a leak.
// MyObject.h
#import <Foundation/Foundation.h>
@class OtherObject;
@interface MyObject : NSObject
@property (strong, nonatomic) OtherObject *other; // Strong reference
- (instancetype)initWithName:(NSString *)name;
@end
// OtherObject.h
#import <Foundation/Foundation.h>
@class MyObject;
@interface OtherObject : NSObject
@property (strong, nonatomic) MyObject *my; // Strong reference
- (instancetype)initWithName:(NSString *)name;
@end
// MyObject.m
#import "MyObject.h"
#import "OtherObject.h"
@interface MyObject ()
@property (strong, nonatomic) NSString *name;
@end
@implementation MyObject
- (instancetype)initWithName:(NSString *)name {
self = [super init];
if (self) {
_name = name;
NSLog(@"MyObject %@ initialized", _name);
}
return self;
}
- (void)dealloc {
NSLog(@"MyObject %@ deallocated", self.name);
}
@end
// OtherObject.m
#import "OtherObject.h"
#import "MyObject.h"
@interface OtherObject ()
@property (strong, nonatomic) NSString *name;
@end
@implementation OtherObject
- (instancetype)initWithName:(NSString *)name {
self = [super init];
if (self) {
_name = name;
NSLog(@"OtherObject %@ initialized", _name);
}
return self;
}
- (void)dealloc {
NSLog(@"OtherObject %@ deallocated", self.name);
}
@end
// main.m
#import <Foundation/Foundation.h>
#import "MyObject.h"
#import "OtherObject.h"
int main(int argc, const char * argv[]) {
@autoreleasepool {
NSLog(@"--- Starting Retain Cycle Demo ---");
MyObject *obj1 = [[MyObject alloc] initWithName:@"Object 1"];
OtherObject *obj2 = [[OtherObject alloc] initWithName:@"Object 2"];
// Create a strong, circular reference
obj1.other = obj2;
obj2.my = obj1;
NSLog(@"Objects created and linked. Notice no dealloc messages will appear.");
}
NSLog(@"--- Retain Cycle Demo Ended ---");
return 0;
}Breaking Retain Cycles with 'weak'
To break a retain cycle, one of the references in the loop must be 'weak' instead of 'strong'. A weak reference does not increase an object's retain count, allowing it to be deallocated when no strong references remain.
Run this fixed example. You'll now see the 'deallocated' messages, meaning no leak!
// MyObject.h
#import <Foundation/Foundation.h>
@class OtherObject;
@interface MyObject : NSObject
@property (strong, nonatomic) OtherObject *other;
- (instancetype)initWithName:(NSString *)name;
@end
// OtherObject.h (FIXED: Using 'weak')
#import <Foundation/Foundation.h>
@class MyObject;
@interface OtherObject : NSObject
@property (weak, nonatomic) MyObject *my; // Weak reference to break the cycle
- (instancetype)initWithName:(NSString *)name;
@end
// MyObject.m
#import "MyObject.h"
#import "OtherObject.h"
@interface MyObject ()
@property (strong, nonatomic) NSString *name;
@end
@implementation MyObject
- (instancetype)initWithName:(NSString *)name {
self = [super init];
if (self) {
_name = name;
NSLog(@"MyObject %@ initialized", _name);
}
return self;
}
- (void)dealloc {
NSLog(@"MyObject %@ deallocated", self.name);
}
@end
// OtherObject.m
#import "OtherObject.h"
#import "MyObject.h"
@interface OtherObject ()
@property (strong, nonatomic) NSString *name;
@end
@implementation OtherObject
- (instancetype)initWithName:(NSString *)name {
self = [super init];
if (self) {
_name = name;
NSLog(@"OtherObject %@ initialized", _name);
}
return self;
}
- (void)dealloc {
NSLog(@"OtherObject %@ deallocated", self.name);
}
@end
// main.m
#import <Foundation/Foundation.h>
#import "MyObject.h"
#import "OtherObject.h"
int main(int argc, const char * argv[]) {
@autoreleasepool {
NSLog(@"--- Starting Fixed Cycle Demo ---");
MyObject *obj1 = [[MyObject alloc] initWithName:@"Object 1"];
OtherObject *obj2 = [[OtherObject alloc] initWithName:@"Object 2"];
// Assign references. obj2 now has a weak ref to obj1.
obj1.other = obj2;
obj2.my = obj1;
NSLog(@"Objects created and linked. Now dealloc messages should appear!");
}
NSLog(@"--- Fixed Cycle Demo Ended ---");
return 0;
}Quick Check: Leak Detection
You've noticed your Objective-C app is slowing down over time and consuming more memory than expected. You suspect memory leaks.
Recap: Mastering Memory
You've learned that memory leaks prevent objects from being deallocated, leading to performance issues. Xcode Instruments, particularly the 'Leaks' template, is your go-to tool for identifying these problems.
A common culprit is the retain cycle, where objects strongly reference each other. You can break these cycles by using weak references (@property (weak, nonatomic)) to ensure proper memory management.
Apprends Objective-C avec un tuteur IA — gratuit
Écris et exécute du vrai code dans ton navigateur, obtiens de l'aide instantanée d'un tuteur IA disponible 24h/24, et reprends là où tu t'es arrêté sur le web ou dans l'app.
- Cours
- 12
- Leçons
- 48
Questions Fréquemment Posées
La leçon « Détection des fuites mémoire avec Instruments » est-elle gratuite ?
Oui — le texte complet de « Détection des fuites mémoire avec Instruments » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Objective-C iOS Development for Legacy & Enterprise Apps, passe à CoddyKit PRO. Le cours Objective-C iOS Development for Legacy & Enterprise Apps comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Détection des fuites mémoire avec Instruments » ?
Utilisez Instruments dans Xcode pour identifier et résoudre les fuites mémoire, les cycles de rétention et les autres goulots d'étranglement liés aux performances mémoire Tu pratiques Objective-C iOS Development for Legacy & Enterprise Apps avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer Objective-C iOS Development for Legacy & Enterprise Apps ?
Aucune expérience préalable n'est requise. Objective-C iOS Development for Legacy & Enterprise Apps sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 1 sur 4.
Combien de temps prend la leçon « Détection des fuites mémoire avec Instruments » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon Objective-C iOS Development for Legacy & Enterprise Apps ?
Oui. Chaque leçon Objective-C iOS Development for Legacy & Enterprise Apps inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Détection des fuites mémoire avec Instruments
- Optimisation du rendu et de la réactivité de l'interface
- Techniques avancées de débogage
- Analyser et réduire le temps de lancement d’une application