Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Finding and fixing Ghostty's largest memory leak

mitchellh.com

Post reply on HN
Print view View original

21–30 of 152 posts

Re: Finding and fixing Ghostty's largest memory leak

#21

Post by dang »

1a527dd5 wrote: post #9
mitchellh wrote: post #5

Earlier quoted context omitted.

What contrast? I stand by what I said there. I just re-read every point and I would say the same thing today and I don't think my blog post contradicts any of that? A user came along and provided a reliable reproduction for me (last night) that allowed me to find and fix the issue. Simultaneously they found the same thing and produced a similar fix, which also helped validate both our approaches. So, we were able to…

[flagged]

Could you please follow the HN guidelines when posting here? They include "assume good faith." and "don't cross-examine".

https://news.ycombinator.com/newsguidelines.html

Re: Finding and fixing Ghostty's largest memory leak

#22

Post by dang »

LgWoodenBadger wrote: post #4

The contrast between the attitude here https://news.ycombinator.com/item?id=46461860 and in this story is a bit wacky to me.

"Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."

https://news.ycombinator.com/newsguidelines.html

Re: Finding and fixing Ghostty's largest memory leak

#23

Post by macote »

quantummagic wrote: post #2

This is great news! Well done to everyone who helped sort it out. It was a problem noted by users in a thread here just last week, https://news.ycombinator.com/item?id=46460319 While Claude Code might have been the reason this bug became triggered by more people, there are some of us who were hitting it without ever having used Claude Code at all. Maybe the assumption about what makes a page non-standard, isn't as bl…

The thread about memory leak is here: https://news.ycombinator.com/item?id=46461061

Re: Finding and fixing Ghostty's largest memory leak

#24

Post by [deleted] »

hotpotat wrote: post #16

speaking of claude code in Ghostty, I’ve noticed I can’t drag and drop images into the prompt when the session is within a tmux pane. I miss that, coming from the mac terminal app, which allowed me to do so. I’d be willing to look into this myself, but mention it in case someone already knows where to start looking.

[deleted]

Re: Finding and fixing Ghostty's largest memory leak

#25

Post by jrpelkonen »

Great write-up. And, thanks mitchellh for Ghostty, I switched to it last year, and have not regretted it.

However, I am a somewhat surprised that the fix is reserved for a feature release in a couple of months. I would have expected this to be included in a bug fix release.

Re: Finding and fixing Ghostty's largest memory leak

#26

Post by mjn »

63 wrote: post #19
mitchellh wrote: post #17

Earlier quoted context omitted.

Static HTML/CSS generated by Opus 4.5. I like using AI for visualizations because it is one-time use throwaway code, so the quality doesn't matter at all (above not being TOTALLY stupid), it doesn't need to be maintained. I review the end result carefully for correctness because it's on a topic I'm an expert of. I produce non-reusable diagrams namespaced by blog post (so they're never used by any other post). I just…

That's really cool. I was looking at them and thinking "I could probably make these with vanilla html/css but it'd be pretty tedious." Perfect use case for AI. I need to work on developing a reflex for it.

I've also started doing this, and it's surprisingly enjoyable to both do and even to read. The end result is often more readable to me than using a 3rd-party JS visualization library, because I only need to know standard HTML/CSS concepts to understand what's going on. And a side benefit is smaller pages with less bitrot due to being able to skip the dependencies.

Re: Finding and fixing Ghostty's largest memory leak

#27

Post by txdv »

LgWoodenBadger wrote: post #4

The contrast between the attitude here https://news.ycombinator.com/item?id=46461860 and in this story is a bit wacky to me.

Only contrast I see is that he thought it was much more of a corner case which turned out to be not that true anymore since everyone started using claude code.

Re: Finding and fixing Ghostty's largest memory leak

#29

Post by 1a527dd5 »

dang wrote: post #21
1a527dd5 wrote: post #9

Earlier quoted context omitted.

[flagged]

Could you please follow the HN guidelines when posting here? They include " assume good faith. " and " don't cross-examine ". https://news.ycombinator.com/newsguidelines.html

Will do my best :)

Re: Finding and fixing Ghostty's largest memory leak

#30

Post by neobrain »

Funny timing, I moved to Ghostty this week and just today I ran into OOM crashes in Ghostty while developing a terminal UI app. Coincidentally this TUI has a tab bar that looks like this, where UTF8 icons are used for recognizability and activity indicators (using © and € as placeholders here):

    1|Flakes ©    2|Installed ©    3|Store © €    4|Security © €
   ──────────────────────────────────────────────────────────────
This works fine normally, but resizing the terminal would quickly trigger the crash - easy to avoid but still annoying!

I was already preparing myself to file a bug report with the easy repro, but this sounds suspiciously close to what the blog post is describing. Fingers crossed :)

(EDIT: HN filters unicode, booo :( )

Post reply on HN