Memory Chronicles: Manage, Trace and Fix Memory Leaks

Transcript

1. 1.

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

   @Gioyik
2. 2.

   Giovanny gio@nodesource.com @gioyik

3. 3.

   © 2019 NodeSourc e What is this really?

4. 4.

   © 2019 NodeSourc e See you at 2pm!

5. 5.

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

6. 6.

   It happens in real life, happens in TNT

7. 7.

   Heap profiler & Timeline

8. 8.

   When to use them?

9. 9.

   Workflow for diagnosing memory leaks?

10. 10.

    TST

11. 11.

    Three Snapshot Technique

12. 12.

    What do the Shallow and Retained Size columns represent?

13. 13.

    Where should I start digging into to discover if I

    have a leak?
14. 14.

    Redacted snapshots

15. 15.

    Core Dumps

16. 16.

    Create a Core dump

17. 17.

    --abort-on-uncaught-exception

18. 18.

    LLDB

19. 19.

    Llnode

20. 20.

    Caveats

21. 21.

    llnode’s coupling to V8

22. 22.

    Promises (?)

23. 23.

    Async / Await FTW!

24. 24.

    Tips for different situations

25. 25.

    Case #1: Server Side Rendering (SSR)

26. 26.

    Case #2: Monitoring tools

27. 27.

    Case #3 Close your connections

28. 28.

    Case #4: Look for agnostic serve pages solution

29. 29.

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

30. 30.

    Case #6: Keep naming you functions

31. 31.

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

32. 32.

    Crazy … right?

33. 33.

    Thank you!