zlacker

[parent] [thread] 2 comments
1. within+(OP)[view] [source] 2026-01-02 07:02:31
Valgrind won’t show you leaks where you (or a GC) still holds a reference. This could mean you’re holding on to large chunks of memory that are still referenced in a closure or something. I don’t know what language or anything about your project, but if you’re using a GC language, make sure you disable GC when running with valgrind (a common mistake). You’ll see a ton of false positives that the GC would normally clean up for you, but some of those won’t be false positives.
replies(2): >>oblio+66 >>Sesse_+vb
2. oblio+66[view] [source] 2026-01-02 08:11:11
>>within+(OP)
Ghostty is written in Zig.
3. Sesse_+vb[view] [source] 2026-01-02 09:06:24
>>within+(OP)
It will, but they will be abbreviated (only total amount shown, not the individual stack traces) unless you ask to show them in full.
[go to top]