Technical Analysis: How Ghostty's Memory Leak Was Identified and Fixed
A few months ago, users started reporting that Ghostty was consuming absurd amounts of memory, with one user reporting 37 GB after 10 days of uptime. Today, I'm happy to say the fix has been found…
Read the full articleYou might also wanna read
Claude Code left 10 CPU-spinning zombie processes running for nearly two days
A software developer discovered that a Claude Code AI session had left behind ten orphaned shell processes silently consuming over 700% CPU
Understanding Garbage Collection and Hunting Memory Leaks in Node.js
Master Node.js memory management with V8 insights and garbage collection techniques. Optimize performance and prevent memory leaks effective
Finding memory leaks with Memtrace
Memory issues can be hard to track down. A function that only allocates a few small objects can cause a space leak if it’s called often enou
GhostLock Exposes a Deeper Linux Kernel Patching Problem
GhostLock's real lesson isn't the bug, it's the eleven weeks most businesses spent unpatched after the fix shipped. Linux kernel patching ne
What was ChatGPT secretly doing on my computer?
No request running overnight, yet 61 Gb, my computer only has 24 RAM, so it probably went digging into the SSD. Should I be concerned? Anyon
GhostRace: Everything you need to know about the data leakage attack in one place
Learn everything about GhostRace, a data leakage attack exploiting speculative execution in computer chips. Discover impact analysis, detect
Comments
Sign in to join the conversation.
No comments yet. Be the first.