stream_terminal crash from HyperlinkSetOutOfMemory

[neurosnap]

Issue Description

I received another report for zmx (via supacode) where a user is reporting a terminal session crashed with an associated macos crash report:

SIGABRT
terminal.Screen.clearCells
terminal.stream.Stream(...).nextNonUtf8
main.daemonLoop
main.Daemon.ensureSession
main.attach

And an associated ghostty warning: [warning] (stream_terminal): error handling VT action action=.linefeed err=error.HyperlinkSetOutOfMemory

I tried tracking it down and it looks like a possible edge case with a page's hyperlink capacity. I will copy my exploration, but here is the report: neurosnap/zmx#182

Following the breadcrumbs:

• stream_terminal log.warn
• vtFallible linefeed
• Terminal.index
• screen.cursorScrollAbove
• screen.cursorScrollAboveRotate
• cur_page.cloneFromRow
• error.HyperlinkSetOutOfMemory

There appears to be some precedence for handling this during certain operations to increase the capacity, but it looks like this code path is simply bubbling the error up.

• insertLines
• deleteLines

I don't fully understand the internals of ghostty here but it looks like there's an edge case with hyperlink capacity and page boundaries?

Expected Behavior

I expect the vt_stream to handle hyperlinks without crashing

Actual Behavior

I receive a SIGABRT from vt_stream.nextSlice()

Reproduction Steps

I had an LLM try to simulate the error in a test case: neurosnap@55edf81

Ghostty Logs

No response

Ghostty Version

ghostty_vt: ghostty-1.3.2-dev-5UdBC8HuDgWFQtz8pKQ-0HH6z0Cb_PKbI0R7AunQhdDF

OS Version Information

macOS: 26.3 (25D125)

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

none

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mitchellh]

I believe this fixes this: #13394