Resposta curta e em inglês, para ler, fechar e treinar em voz alta.
A leak retains memory that the application no longer needs. Reachable references can keep JavaScript objects alive, while native resources can also leak outside the JS heap.
Compare memory retained after GC under comparable workloads. Inspect heap, external memory, RSS, and allocation patterns. Common causes include unbounded caches, listeners never removed, and closures retaining large objects.
Find the retaining path, fix ownership or cleanup, and repeat the workload. Heap snapshots can pause the process and require substantial extra memory, so capture them only on an instance that can tolerate that impact. A growing RSS alone does not prove a JS heap leak.
Ler é o primeiro passo. No app, essa pergunta vira flashcard com repetição espaçada, e o módulo tem quiz e simulado para testar o que ficou.
Treinar essa pergunta no app