Fix possible memory leaks

[WilliamHCarter]

What do you want to change?

I’d like to contribute a few bug fix PRs over time surrounding possible memory leak edge cases.

I’ve been working on a small set of memory safety tools for zig, originally inspired by the dialog surrounding Bun’s Rust port. One of these tools (static AST analyzer) has gotten pretty decent at finding edge cases where lax cleanup can lead to leaks in a few different cases.

Long story short I’ve manually verified a few findings for Ghostty, and in cases where I can repro and feel confident explaining what’s occurring, I’d like to contribute the fixes as small bugfix PRs. (I have a few merged PRs for libvaxis in the same vein, if you'd like to check out an example)

Short note on AI: No AI is used by the tool to find these bugs, and I’m not using any AI for the fixes either. That being said, I’ve used quite a bit of AI in the process of developing the toolset. I don’t believe that violates any of the guidelines listed here, happy to go over my process in more detail if more explanation is needed.

Why do you want to make this change?

I want to help create a more secure zig software ecosystem. I use Ghostty every day, and if I can help make it more secure or performant I’d love to.

I'm aware this proposal is a bit vague, wasn't quite sure whether to put this in as one bug fix on vouch and then simply open others if the process goes through, but since the bugs are largely unrelated in terms of location I thought it best just to describe my intentions.

I acknowledge that:

• I have read the Contributing Guide and understand the contribution process.
• I have read and agree to follow the AI Usage Policy.
• I wrote this vouch request myself, in my own voice, without AI generating it.

[jcollie]

!vouch