Repository navigation
ghostty crashes after lots of cursor movement and replacing text, then resizing window (contains debug log and repro file) #7977
Issue Description#3885 was fixed in #7537, but that hasn't solved the crashes I've been experiencing. My most recent crash was immediately after running After running I've also been able to reproduce this crash by resizing the window from half screen width to full screen width. The crash does NOT happen when the window is resized vertically, changing the number of lines. It takes changing the number of columns, and therefore reflowing the text in the terminal window, to cause the crash. But I can reproduce it consistently: run Expected BehaviorGhostty doesn't crash when resized horizontally and reflowing text. Actual BehaviorCrash when Ghostty is resized from full screen width to half screen width, or from half screen width to full screen width, after a lot of characters have been overwritten in the terminal. Reproduction Steps
Alternately, gunzip the file attached to #7977 (comment) and cat it to the terminal. (It's a log made with the Ghostty LogsGhostty VersionOS Version InformationArch Linux (Linux only) Display ServerWayland (Linux only) Desktop Environment/Window ManagerHyprland 0.50.0 Minimal Ghostty ConfigurationNone whatsoever: commented out every line of my Ghostty config and I can still reproduce the crash by running `dotnet build` and then resizing the width of the Ghostty window.Additional Relevant ConfigurationI'm running .NET SDK version 9.0.302. In .NET 8 and previous, the default output of However, when I tried to reproduce this behavior by running I acknowledge that:
|
Replies: 8 comments 6 replies
|
Most relevant lines from the log file are probably these: Each of those "adjusting page capacity" messages came around the same time I was noticing significant stutter (several seconds of output lag, in some cases) in the Ghotty terminal window. Also of note is that Where the So I'm guessing that the way .hyperlink_bytes kept increasing may be part of the issue. The NU1701 warning (with a colon after it) was one of the first lines printed, and the constantly-changing text was underneath that. So my suspicion is that the hyperlink-parsing code was constantly trying to parse and re-parse the characters following |
|
Also occurs with version 1.1.4-main+7d9904207 (latest Git commit as of when I'm writing this). |
|
Those logs are really long and tedious to scroll through. I'll edit them down to just what I think are the relevant sections. I've attached a gzip of the complete log text, edited only slightly to redact the name of the C# project I'm working on. (It would almost certainly be fine for me to disclose the project name, but I'd rather err on the side of caution). |
|
More findings: I can reproduce this quite consistently when But a brand-new Ghostty window (and process), with a successful |
|
More data: I tried to check out older commits from the Git repo in order to run a So this appears to not be a regression, at least not one introduced in the past few months. |
This comment has been hidden.
This comment has been hidden.
|
Here's a transcript of running |
Moved to #8009