panic(cpu 0 caller 0xffffff8007a91b2c): Sleep transition timed out after 180 seconds while calling power state change callbacks
Thanks for filing an issue! Please answer the questions below so I can help you.
-
iTerm2 version: Build 3.3.9
-
OS version: ProductName: Mac OS X ProductVersion: 10.15.4 BuildVersion: 19E287
-
Attach com.googlecode.iterm2.plist here (drag-drop from finder into this window)
-
Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog : System rebooted after os crashed. Can provide if requested, anticipating repro might be needed to gather the full logs.
-
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 : No or issue does not fall in those categories.
-
Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logsproactive_event_tracker_2020-05-14-073124.diag
-
Are you reporting excessive memory usage? Please attach a heap analysis: https://gitlab.com/gnachman/iterm2/wikis/heapshot
Detailed steps to reproduce the problem:
- Scenario : User uses iterm normally through the day on the mac. Then closes macbook lid at end of the day.
- Closes macbook pro lid end of the day.
What happened: Next morning. When user tries to login to the computer, it appears as though the system just booted up. Login takes far longer. Upon login, user is greeted with mac os message that computer was restarted due to a problem. Other applications or windows might have disappeared too and user needs to reload missing stuff.
This is a fairly consistent experience, whenever user forgets to quit iterm before having the macbook sleep for an extended time. The same issue never seems to happen if user uses only built-in terminal instead.
So far, haven't found settings to have iterm and macos co-exist, after closing the lid.
What should have happened: System should not have crashed when closing macbook lid with iterm running.