Daily iTerm crashes
Crash report
Howdy!
I've been having daily iTerm crashes over the last 6 months or so and haven't been able to pinpoint why it's crashing.
- iTerm2 version: Build 3.5.0beta10 (but it has occurred on previous versions for the last 6-10 months or so on stable and beta versions)
- OS version: 13.4
- com.googlecode.iterm2.plist
- iTerm2-2023-06-06-170923.ips
- iTerm2-2023-06-04-185301.ips
- iTerm2-2023-06-03-144202.ips
I tried taking a screen recording but I can't reliably reproduce it.
You probably have a lot of crash reports from me (Sam McLeod) over the last year.
Detailed steps to reproduce the problem
What happened
Today
- One of my regular iTerm daily crashes occurred and I had to force kill iTerm which was beach-balling.
- I reopened and enabled debug logs.
- I noticed that my fonts looked strange.
- I checked the profile and my font was unset.
- I set it back to my font (IBM Plex Mono) and that was OK, but it was the wrong size.
- I set the font to 20 and iTerm crashed.
- I was able to repeat the font size crash several times, then it seemed fine and I can no longer replicate this specific crash.
Other days
I'll switch to iTerm and one of two things will happen, either:
A) iTerm won't be running and I've found it's crashed (if macOS's crash reporter is enabled - it shows up).
Looking over the crash logs something I've seen a few times relates to a stack buffer overflow in the "VT100Grid" class, specifically in the "debugString" method.
or
B) iTerm will be running but it will be frozen and if I mouse over the menu bar I can see it's beach-balling.
I've seen segmentation faults at address 0x3333333333333373 while the background process role.
This occurs between every 2-3 days, to 2x daily, I can't find a pattern with the days it crashes.
What should have happened
- Should not crash daily.
- When starting after a crash - the reason for the crash or at least the log/log location should be presented to the user.
I'm really keen to get to the bottom of why it crashes so much for me - please do reach out, my email is in the crash reports submitted in-app if you need it. I'm more than happy to run any debugging commands etc....
Thanks,