iTerm2 crashing on session input from various tmux versions with iTerm2 attach/create
iTerm2 Version
- 3.4.2 running on macOS 10.15.7.
tmux Versions
- tmux v2.8 on Linux distro Debian 10.6 x86_64
- tmux v2.9a on Linux distro CentOS 6.10 x86_64
- tmux v3.1c on macOS 10.15.7 x86_64
plist File com.googlecode.iterm2.plist: com.googlecode.iterm2.plist
Crash Logs
-
Crash log 1 (tmux 2.8) (tmux -CC -u new-session, followed by creation of a few tabs): crashlog_new_tmux_session_1.txt
-
Crash log 2 (tmux 2.8) (tmux -CC -u attach, with one of the attached instances having a few dozens of kilobytes of data output in its buffer): crashlog_2_tmux_attach.txt
-
Crash log 3 (tmux 2.9a) (tmux -CC attach, no '-u' unicode flag on this launch): crashlog_3_tmux_attach_no_unicode_-u_flag.txt
-
Crash log 4 (tmux 3.1c) (tmux -CC -u new-session, followed by ps aux): crash_log_4_tmux_3.1c.txt
Environment Conditions
macOS 10.15.7 x86-64, using three different tmux versions on two different remote Linux servers and one on my local macOS workstation, each supporting the -CC flag; some sessions made new, others attached, some launched with or without unicode -u mode.
Reproduce the Issue
- Create a tmux session (tmux -CC -u new-session) followed by either command that generates dozens of lines of output OR attach to a session with existing larger output buffers. Crash. That's it.
Context Note
I've used iTerm2+tmux -CC's 'native window mode' every day for the past several years. Each day I attach to anywhere from one to eight different tmux sessions via 'tmux -CC -u'. I've had virtually zero crashes with iTerm2. These crashes started last night and I am not sure why. I have not updated libraries on my end nor the remote servers that run tmux' end.