iterm2 + OMZ + Mac M2

247 views
Skip to first unread message

Milind Vaidya

unread,
Feb 17, 2024, 11:18:06 AM2/17/24
to iterm2-discuss
Hi 

I have following config

Mac book pro : Apple M2 chip
OS : Ventura 13.3.1(a)


Issue : 
1. Restart mac
2. Launch iterm2 terminal with OMZ
3. Everything works fine for few days
  • Fuzzy finding with OMZ 
  • File Name completion 
  • nvim opens file pretty fast
  • Tabs open smoothly for iTerm
4. Then is starts getting slow after few days
  • Fuzzy finding slows or stops working
  • File Name completion slows considerably 
  • nvim opens file very slowly
  • Tab command ( Commad + T ) does not open tab
  • If I close iTerm completely and try to relaunch it does not open window flashes and nothing happens
When I restart the laptop things go back to normal.

I have encountered this already 5-6 times since I got this laptop few months ago. Nothing else like chrome etc has such performance degradation problem.

Thanks,
Milind 

George Nachman

unread,
Feb 21, 2024, 4:19:35 PM2/21/24
to iterm2-...@googlegroups.com
If cmd-t doesn’t work or is very slow then that suggests that it’s iTerm2 that’s getting slow, not your shell. Please file an issue and attach a sample. See here for instructions: https://gitlab.com/gnachman/iterm2/-/wikis/HowToSample

--
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/fa9ec238-e9fe-42a9-8858-d4b34f2e4087n%40googlegroups.com.

Milind Vaidya

unread,
Mar 3, 2024, 8:10:32 PM3/3/24
to iterm2-discuss
Thanks for the instructions.

I was waiting for the issues to reoccur and today it did. I am not able to create a new tab with Cmd + t or by clicking + sign

It have been almost 11-12 days I am working on my laptop without restarting or switching it off
iTerm terminal is constantly running.

Attaching the sample with this mail. 

Moreover 
$git add Reve + tab : it took 11.38 seconds before completing the command git add Reverse.java

Hope this helps
iTerm2-No-Tab-Opening.txt

George Nachman

unread,
Mar 5, 2024, 8:21:39 PM3/5/24
to iterm2-...@googlegroups.com
The app appears to be idle in the sample.

Do you think you could make a debug log wherein you press cmd-t and it doesn’t work? Instructions are here: https://iterm2.com/debuglog

Milind Vaidya

unread,
Mar 7, 2024, 12:01:53 AM3/7/24
to iterm2-...@googlegroups.com
Sure. I will give it a try.
But it seems due to that issue the iterm became slow, even opening file with vim started taking long time
Eventually the mac restarted and iterm is normal now.

But I will follow up and wait till the issue reoccurs, it may take a few days.
 

You received this message because you are subscribed to a topic in the Google Groups "iterm2-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/iterm2-discuss/HfVruKDf1eM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to iterm2-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/iterm2-discuss/CAB5Rqo%3Dfogs%3DdY72b1sQG2SEnT0iD6dj26Mu4Hxz4WFDw-CaRg%40mail.gmail.com.

Milind Vaidya

unread,
Mar 12, 2024, 1:37:00 AM3/12/24
to iterm2-discuss
Hi 

I encountered the same issue again. The deteriorating pattern was same.
1. I have 3 tabs open in iterm
2. It was fast to begin with when the mac had restarted
3. After couple of days everything started getting slower e.g. command completion, execution, opening file in vim
4. and then again today Cmd + t is not opening new tab or + sign also not opening new tab.

Attaching here the debug logs
debuglog.txt

Julian Elischer

unread,
Mar 20, 2024, 9:32:17 PM3/20/24
to iterm2-discuss
if you see things getting really slow on the mac and you have multiple spaces, try killing the "dock" app.
I've seen a bug over the mast few years where Dock goes to 100% CPU staving out everything else and eventually the session restarts, (note: not a system reboot.. )

I keep an activity monitor in background to see it happening and that has a 'kill the app" option. which is convenient because when it happens it takes minutes for the "force quit" dialog to appear and by then the session has reset.
Reply all
Reply to author
Forward
Message has been deleted
0 new messages