0Pricing
Objective-C iOS Development for Legacy & Enterprise Apps · Aula

Detecção de vazamentos de memória com Instruments

Utilize o Xcode Instruments para identificar e resolver vazamentos de memória, ciclos de retenção e outros gargalos de desempenho relacionados à memória.

Detecção de vazamentos de memória com Instruments é uma aula grátis de Objective-C iOS Development for Legacy & Enterprise Apps no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Objective-C iOS Development for Legacy & Enterprise Apps, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Objective-C iOS Development for Legacy & Enterprise Apps inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

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.

Perguntas Frequentes

A aula “Detecção de vazamentos de memória com Instruments” é grátis?

Sim — o texto completo de “Detecção de vazamentos de memória com Instruments” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Objective-C iOS Development for Legacy & Enterprise Apps, atualize para CoddyKit PRO. O curso de Objective-C iOS Development for Legacy & Enterprise Apps inclui 4 aulas no total.

O que vou aprender em “Detecção de vazamentos de memória com Instruments”?

Utilize o Xcode Instruments para identificar e resolver vazamentos de memória, ciclos de retenção e outros gargalos de desempenho relacionados à memória. Você pratica Objective-C iOS Development for Legacy & Enterprise Apps com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Objective-C iOS Development for Legacy & Enterprise Apps?

Nenhuma experiência prévia é necessária. Objective-C iOS Development for Legacy & Enterprise Apps no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Detecção de vazamentos de memória com Instruments”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Objective-C iOS Development for Legacy & Enterprise Apps?

Sim. Cada aula de Objective-C iOS Development for Legacy & Enterprise Apps inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Detecção de vazamentos de memória com Instruments
  2. Otimização da renderização e da responsividade da interface
  3. Técnicas avançadas de depuração
  4. Analisar e Reduzir o Tempo de Arranque da Aplicação
← Voltar para Objective-C iOS Development for Legacy & Enterprise Apps