High CPU usage
281 views
Skip to first unread message
Allison NEWMAN
Jun 5, 2019, 10:02:27 AM6/5/19
to iterm2-discuss
Has anyone else noticed high CPU usage on the current build? (Build 3.2.9)
I'm ssh-ing to a remote PC and then launching a compilation in a tmux environment, and I'm seeing iTerm2 use over 100% of the CPU for extended periods of time, which seems pretty crazy for a window of scrolling text. This is running on a current MacBook Pro 13 inch - no touchbar, so I really wouldn't expect the workload to be driving the fans.
George Nachman
Jun 15, 2019, 12:21:10 AM6/15/19
to iterm2-...@googlegroups.com
Would you mind making a sample with activity monitor?
On Wed, Jun 5, 2019 at 7:02 AM Allison NEWMAN <allison...@netgem.com> wrote:
Has anyone else noticed high CPU usage on the current build? (Build 3.2.9)I'm ssh-ing to a remote PC and then launching a compilation in a tmux environment, and I'm seeing iTerm2 use over 100% of the CPU for extended periods of time, which seems pretty crazy for a window of scrolling text. This is running on a current MacBook Pro 13 inch - no touchbar, so I really wouldn't expect the workload to be driving the fans.
--
You received this message because you are subscribed to the Google Groups "iterm2-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iterm2-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iterm2-discuss/9ab5344a-2491-4fe7-b004-5baabf627427%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Julian Elischer
Mar 29, 2021, 1:27:52 PM3/29/21
to iterm2-discuss
I'm seeing this occasionally now.. on catalina. For a while all will be ok with a dozen or so tmux sessions open and then the fan will come on and when I look, "top -ocpu" will show iTerm2 as being the highest consumer of CPU. with numbers between 50 and 115% of a cpu.
The way to stop it is to detach all the tmux sessions, and restart iterm2. Then things go back down to 10% or so after reattaching the sessions. If you want more information I'm happy to catch it next time this happens but you need to be really specific as to what you want and how I get to it... (menu entries or commands).
The way to stop it is to detach all the tmux sessions, and restart iterm2. Then things go back down to 10% or so after reattaching the sessions. If you want more information I'm happy to catch it next time this happens but you need to be really specific as to what you want and how I get to it... (menu entries or commands).
Reply all
Reply to author
Forward
0 new messages