Potential Memory Leak or Significant Increase in Memory Footprint between beta2 and beta3
- iTerm2 version: Build 3.2.6beta3
- OS version: 10.14.2 Beta (18C38b)
- Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window) [No can do. I backed down to beta2 before attempting to file the performance issue]
- Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog [No crash / debug log was taken ....]
- Are you reporting a performance issue or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample [PERFORMANCE ISSUE - Potential Memory Leak]
- Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs [NO]
- Are you reporting excessive memory usage? Please attach a heap analysis: https://gitlab.com/gnachman/iterm2/wikis/heapshot [Um, Yes I think so but I'd need to upgrade to beta3 to do so properly ...]
Detailed steps to reproduce the problem:
I run at least 55 shell tabs in 4 windows. 51 are running the same shell script though the data in each migrates away from initially established settings over time ..... You cannot reproduce this environment easily ..... I'd be happy to take direction and drive some testing in detail to help you understand/find the issue soonest.
What happened: I suspect that beta3 has a memory leak of some sort -OR- in the upgrade from beta2 to beta3 you've intentionally increased the footprint of iTerm2, maybe significantly. So what happens: I start my environment in the usual way and all runs well for a period of time. How much time everything runs well depends upon how heavily I drive the 51 scripts (I've been known to drive loads of 150+ for 15 mins or more when I get everything going).
Suddenly my ability to switch between tabs takes forever (15-30 secs). During the wait I see the beachball spinning. Once the time has passed typing within the tab performs as normal. Starting some other app (any other app) takes forever (again 15-30 secs), more beach balling as I wait. Once an app "comes alive" it performs as normal - as long as I don't attempt to switch to yet another app or back to iTerm2. Given that iTerm2 was the only thing to change in my environment, I decided to kill off all of its tabs to measure any new effects. Result - NADA - starting a new tab takes forever (as defined above). Switching to another app takes forever as well. So, I then kill off iTerm2 altogether. Now switching to another app (I tried with a series of apps) works as normal. Starting iTerm2 again and starting up my litany of tabs all works as normal - but only for a period of time - then - back to tab switching and app switching delays. I want to point out (again) that killing off the tabs e.g. causing the shell scripts to exit had no apparent effect on addressing the issue. Killing off iTerm2 altogether did the trick.
I suspect the delays are due to memory swapping; my main drive goes nuts as I wait.
I have a memory stats monitor running on my system. Under beta2 with all scripts initialized I'm using about 1/3 of my memory. Under beta3, given the same circumstances, I'm using closer to 60% of the memory; not quite doubled but significant in my view.
What should have happened: ThenToBeta2, I've run my environment without any hiccups. I'd like to get back to this state obviously with Beta3.