Memory Chronicles: Manage, Trace and Fix Memory Leaks

8cf49d39d44f100e1afed5c5a259fed4?s=47 Giovanny Gongora
December 12, 2019
Technology
0
9

Memory Chronicles: Manage, Trace and Fix Memory Leaks

Talk at Node+JS Interactive 2019

8cf49d39d44f100e1afed5c5a259fed4?s=128

Giovanny Gongora

December 12, 2019
Tweet

More Decks by Giovanny Gongora

See All by Giovanny Gongora
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
0
6
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
0
11
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
1
18
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
1
400
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
0
110
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
1
48
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
0
420
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
0
110
8cf49d39d44f100e1afed5c5a259fed4?s=48 gioyik
0
99

Other Decks in Technology

See All in Technology
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
2.6k
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
110
2aea20b60d544d0dcccb70a4bb6af648?s=48 hminamiohtsu
0
120
7cd783377515bdf8207062840b7b2f4e?s=48 soracom
0
110
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
130
5ad0bb268dd2605b09165d464308cb7e?s=48 igaiga
4
260
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
170
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
240
20451295e0cb4dce2b2805b2a61cd92d?s=48 tnk4on
1
320
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
220
Dafc4723e9a1c067796c0fec6f509774?s=48 lemiorhan
4
690
Eebedc2ee7ff95ffb9d9102c6d4a065c?s=48 line_devday2020
0
320

Featured

See All Featured
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
683
180k
44b54d2ffcb7857004071cc6795dde11?s=48 cassininazir
346
20k
E76911cbe088e5b850d966de3fc7435b?s=48 robhawkes
52
2.7k
016edace78ffe826f2348d1e0c504afd?s=48 maggiecrowley
7
340
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
310
21k
1519587b1a0febb658c36c94f6272b0d?s=48 roundedbygravity
241
21k
245cee81a9c424266e5e401d844ea881?s=48 lara
15
2.5k
4262b9cfacfb6b2c77f23e1d0310cd3e?s=48 myddelton
107
11k
168ccec72eee0530b818d44f3fedaacf?s=48 shlominoach
175
7.3k
1519587b1a0febb658c36c94f6272b0d?s=48 roundedbygravity
84
7.8k
A16eb159db895e3b01d3dc95767ad595?s=48 jonyablonski
10
820
E195ae45320d9202eaa01c9f1d31a416?s=48 marktimemedia
5
250

Transcript

  1. Memory Chronicles: Manage, Trace and Fix Memory Leaks Giovanny Gongora

    @Gioyik

  2. Giovanny gio@nodesource.com @gioyik

  3. © 2019 NodeSourc e What is this really?

  4. © 2019 NodeSourc e See you at 2pm!

  5. Who had a memory issue with a Node.js application before?

  6. It happens in real life, happens in TNT

  7. Heap profiler & Timeline

  8. When to use them?

  9. Workflow for diagnosing memory leaks?

  10. TST

  11. Three Snapshot Technique

  12. What do the Shallow and Retained Size columns represent?

  13. Where should I start digging into to discover if I

    have a leak?

  14. Redacted snapshots

  15. Core Dumps

  16. Create a Core dump

  17. --abort-on-uncaught-exception

  18. LLDB

  19. Llnode

  20. Caveats

  21. llnode’s coupling to V8

  22. Promises (?)

  23. Async / Await FTW!

  24. Tips for different situations

  25. Case #1: Server Side Rendering (SSR)

  26. Case #2: Monitoring tools

  27. Case #3 Close your connections

  28. Case #4: Look for agnostic serve pages solution

  29. Case #5: Review you <THIS-to-THIS> packages

  30. Case #6: Keep naming you functions

  31. Case #6: Check how reliable are your 3rd services

  32. Crazy … right?

  33. Thank you!