@mitchellh what did you use for the memory visualizations? Looks nice, and the website plays well with mobile. Whats the stack?
Finding and fixing Ghostty's largest memory leak
11–20 of 152 posts
Re: Finding and fixing Ghostty's largest memory leak
#12Earlier 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]
Dupes are not deleted, you can just search for them and see that there are not that many of those, and that's with this not being the only unsolved memory leak (https://github.com/ghostty-org/ghostty/discussions/9314 is a different one).
Re: Finding and fixing Ghostty's largest memory leak
#13The contrast between the attitude here https://news.ycombinator.com/item?id=46461860 and in this story is a bit wacky to me.
I think there's only a perceptible "attitude" difference if you are fired up by the fact that they are conservative about using the "issues" tab.
Re: Finding and fixing Ghostty's largest memory leak
#14The contrast between the attitude here https://news.ycombinator.com/item?id=46461860 and in this story is a bit wacky to me.
Presumably that discussion is the reason this was fixed. Very bizarre bug tracking policy IMO.
No, the reason it was fixed is that somebody managed to reliably reproduce the issue: https://github.com/ghostty-org/ghostty/discussions/10244
As you can see, there's no hint or evidence they even are on HN let alone saw that discussion.
Re: Finding and fixing Ghostty's largest memory leak
#15The contrast between the attitude here https://news.ycombinator.com/item?id=46461860 and in this story is a bit wacky to me.
Super weird take. Why treat the guy as if he’s a bad actor? All of the public evidence shows good faith on this issue and on the project in general. We’ve also had a clear explanation of why discussion precedes issue creation.
Re: Finding and fixing Ghostty's largest memory leak
#16speaking 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.
Re: Finding and fixing Ghostty's largest memory leak
#17@mitchellh what did you use for the memory visualizations? Looks nice, and the website plays well with mobile. Whats the stack?
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 sanity check that the implementation isn't like... mining bitcoin or leaking secrets (my personal site has no secrets to build) or something. After that, I don't care at all about that quality.
The information is conveys is the critical part, and diagrams like this make it so much more consumable for people.
Re: Finding and fixing Ghostty's largest memory leak
#18@mitchellh what did you use for the memory visualizations? Looks nice, and the website plays well with mobile. Whats the stack?
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 reasonable, thanks!
Re: Finding and fixing Ghostty's largest memory leak
#19@mitchellh what did you use for the memory visualizations? Looks nice, and the website plays well with mobile. Whats the stack?
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.
Re: Finding and fixing Ghostty's largest memory leak
#20Super accessible write up as someone unfamiliar with Ghostty and terminal emulators in general. Thanks!