On Big Sur, session restoration will eventually kill the shell in iTerm and Terminal.app

Thanks for filing an issue! Please answer the questions below so I can help you.

• iTerm2 version: 3.3.11
• OS version: macOS 11.0 Beta (20A4299v)
• Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window) com.googlecode.iterm2.plist
• Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog
• Attach a screen capture video if it would make the reproduction steps clearer.
• Are you reporting a performance issue, excessive CPU usage, or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample
• Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs
• Are you reporting excessive memory usage? Please attach a heap analysis: https://gitlab.com/gnachman/iterm2/wikis/heapshot

PLEASE ATTACH YOUR PLIST FILE FOR BUG REPORTS! Seriously! I'll probably ask you for it if you don’t.

Detailed steps to reproduce the problem:

1. With session restoration enabled, open multiple terminal sessions in iTerm
2. Close them without explicitly typing exit

What happened:

After a fairly short period of time the iTerm won't present a shell, only a cursor. Terminal.app will respond the same at this point and the Mac won't cleanly shutdown.

What should have happened:

Sessions should continue to work.

Workaround:

Disabling Enable session restoration under Preferences > Advanced > Session resolves prevents the hang ups, albeit with the obvious loss of functionality.