News for hackers. Stuff that matters.

A comment on Why users cannot create Issues directly. Parent comment

Re:Why users cannot create Issues directly by rorytbyrne on Friday January 02, 2026 @08:27AM (#46464501)
I spotted Ghostty using 20GB+ memory a few days ago on MacOS (according to Activity Monitor). I went through all my tmux sessions, killed everything, it was still 20GB+ so I re-started Ghostty. If I see it happen again, I'll take some notes.
[ Parent | on HN ]
Re:Why users cannot create Issues directly by wizzwizz4 on Friday January 02, 2026 @12:03PM (#46466828)
Complete speculation, but does tmux use the xterm alternative screen buffer? I can see a small bug in that causing huge memory leaks, but not showing up in testing.
[ Parent | on HN ]
Re:Why users cannot create Issues directly by xpe on Friday January 02, 2026 @09:21AM (#46464989)
On some level, that's impressive. Any idea of how long Ghostty was alive? Maybe this a new feature where Ghostty stores LLM model parameters in the terminal scrollback history? /s
[ Parent | on HN ]
Re:Why users cannot create Issues directly by rorytbyrne on Friday January 02, 2026 @02:01PM (#46468128)
Not which parts of this are sarcastic or not, but it was probably running for a few weeks. High variance on that estimate though. I was running 5+ Claude Code instances and a similar number of vim instances.
[ Parent | on HN ]