using memray to debug (and fix) a memory leak in krb5! (advanced) anthony explains

[@nometutentegiapreso]

This is literally one of my favourites tech channels, the content keeps getting greater and greater 😍 thank you for sharing Anthony

[@ethanmye-rs]

Very nice, finding bugs in old code is always so satisfying. Sorry it wasn’t a bug in Postgres, but still very impressive!

[@drz1]

memray and the team behind it are just top class

[@bryanbanda]

Love these rabbit holes, that was a neat find!

[@Asgallu]

Great video

[@Khushpich]

very interesting, great work!

[@RuslanKovtun]

18:06 - oh, yeah, made me laugh too much

[@jonahturner2969]

memray is the shit, so good

[@amir.hessam]

Very cool; learned a new tool; Thanks Anthony

[@KishanPatel-nd3yb]

This is very cool.

[@yomajo]

Deep.

[@apstl7106]

Antony! Can you talk about Hatch?

[@Maxible]

1. This is super cool 2. You're using macOS specific tools from a Linux system and that hurt my brain for a minute 🙃

[@anthonywritescode]

yeah I'm `ssh`'d into a mac here

[@Maxible]

@@anthonywritescode I figured it was that but for a second I was like, "wait, what?"

[@RuslanKovtun]

Do you know that you can click on flamegraph to expand subtree for easier viewing?

[@anthonywritescode]

yes of course I do

[@RuslanKovtun]

@@anthonywritescode just found it strange that you haven't used this feature when was looking for the leaking node, that is why I assumed.. Anyway, thank's for the vids, they are always helpful.

[@anthonywritescode]

yeah I knew what the shape of it was supposed to look like and none of the ones there matched it. the big allocations (not actually leaked) in redis were making it ~relatively insignificant so it wasn't even showing up in the flamegraphs

[@charlesrussell6183]

nerd nerd nerd... love it

[@AS-zj4jv]

cutie