using memray to debug (and fix) a memory leak in krb5! (advanced) anthony explains
Вставка
- Опубліковано 5 вер 2024
- today I show how I utilized memray to both find, debug, and ultimately fix a memory leak in krb5 -- sadly this was not the leak I was looking for though!
playlist: • anthony explains
==========
twitch: / anthonywritescode
dicsord: / discord
twitter: / codewithanthony
github: github.com/aso...
stream github: github.com/ant...
I won't ask for subscriptions / likes / comments in videos but it really helps the channel. If you have any suggestions or things you'd like to see please comment below!
This is literally one of my favourites tech channels, the content keeps getting greater and greater 😍 thank you for sharing Anthony
Very nice, finding bugs in old code is always so satisfying. Sorry it wasn’t a bug in Postgres, but still very impressive!
Love these rabbit holes, that was a neat find!
memray and the team behind it are just top class
18:06 - oh, yeah, made me laugh too much
Very cool; learned a new tool; Thanks Anthony
very interesting, great work!
1. This is super cool
2. You're using macOS specific tools from a Linux system and that hurt my brain for a minute 🙃
yeah I'm `ssh`'d into a mac here
@@anthonywritescode I figured it was that but for a second I was like, "wait, what?"
This is very cool.
memray is the shit, so good
Deep.
Antony! Can you talk about Hatch?
nerd nerd nerd... love it
Do you know that you can click on flamegraph to expand subtree for easier viewing?
yes of course I do
@@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.
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
cutie