Replies: 5 comments 2 replies
-
I had another crash today. Same error as before.
Version of ghostty:
And I've submitted the crash report via Sentry:
Logs before and after the above error
|
Beta Was this translation helpful? Give feedback.
-
I've been seeing this issue every time I hit the resize button. The crash seems severe and affects all ghostty instances (windows). The only way to revive is to do a force-quit on the Mac. By then all work is lost. I'm able to launch a new window, however, it also becomes unresponsive immediately. Sorry, I couldn't find any crash file like @pkazmier posted, so unable to provide any logs/dumps. |
Beta Was this translation helpful? Give feedback.
-
Running a tip build with 1.0.2 seems... pretty out of date. Does a more recent tip build work? I can't reproduce this on the latest HEAD |
Beta Was this translation helpful? Give feedback.
-
This might be related to #5635; as @taylrfnt said try upgrade your copy. If you know what you did before it crashed, or any reproduction steps, that would be helpful too. |
Beta Was this translation helpful? Give feedback.
-
I still have regular crashes with Ghostty with daily updates on tip. I just have not had time to help troubleshoot. If I have time this weekend, I’ll compile a debug build and see if I can reproduce. It has something to do with my obsession of constantly changing fonts and sizes. |
Beta Was this translation helpful? Give feedback.
-
Tonight Ghostty crashed on me. Fortunately, I've been tailing logs in WezTerm, so I was able to see the error message:
I also submitted the crash report via Sentry CLI based on the instructions provided in README:
I'm sorry I don't have the version info handy (I use tip). I had copied the output, but forgot to paste, and unfortunately I've since updated as the pop-up showed up. But it was likely a version from earlier today as I update frequently. Here is the version output of the one I'm running now as the other details might be helpful:
The only other thing I can add is that I've been tracking memory usage as it seems a bit high. Mac Activity Monitor showed 1.4GB for Memory at the time if I recall. I know that number means nothing, but Real Memory was around 600MB. This would only have been for less than a day's worth of usage. At the time of the crash, I think I had just reloaded my configuration as I've been having way too much fun playing with shaders.
If it occurs again, I'll try and collect more info for you.
Beta Was this translation helpful? Give feedback.
All reactions