iterm2 freezes on switching to it or between commands

[diez.r...@ableton.com]

Hi,

I'm a happy iTerm2-user for years. But since a few weeks ago, it has become barely usable (so I even switched to Terminal.app in between).

The reason are weird stalls/freezes. They occur when e.g. switching to iterm2 using Cmd-Tab. I get a spinning beach-ball for a couple of seconds. There are similar problems when using it, then it happens between commands. Of course this happens intermittently, as those things go :(

iTerm2 version: 3.1.5.beta.1

macOS: 10.12.6 (16G29)

Any suggestions how to get to the bottom of this?

Cheers,

Diez

[Hendrik Visage]

Okay , so I'm not going mad trying to find this problem I thought were related to my disks going bad and after I've reinstalled on spanking brand new firecudas, it's still there

Build 3.1.4

 

[George Nachman]

I'm chasing down some issues related to this. It seems like it's related to network file systems. Is it possible you have a network mount? 

It would also be useful to get a sample, as described here: 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-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hvjunk]

On 04 Nov 2017, at 22:43 , George Nachman <gnac...@llamas.org> wrote:

I'm chasing down some issues related to this. It seems like it's related to network file systems. Is it possible you have a network mount? 

At least one NFS, possibly a 2nd or third (APFS)

It would also be useful to get a sample, as described here: https://gitlab.com/gnachman/iterm2/wikis/HowToSample

Will try the next time it happens.

On Mon, Oct 30, 2017 at 8:09 AM, Hendrik Visage <hvj...@gmail.com> wrote:

On Monday, October 30, 2017 at 1:39:48 PM UTC+2, diez.r...@ableton.com wrote:

Hi,

I'm a happy iTerm2-user for years. But since a few weeks ago, it has become barely usable (so I even switched to Terminal.app in between).

The reason are weird stalls/freezes. They occur when e.g. switching to iterm2 using Cmd-Tab. I get a spinning beach-ball for a couple of seconds. There are similar problems when using it, then it happens between commands. Of course this happens intermittently, as those things go :(

iTerm2 version: 3.1.5.beta.1

macOS: 10.12.6 (16G29)

Any suggestions how to get to the bottom of this?

Okay , so I'm not going mad trying to find this problem I thought were related to my disks going bad and after I've reinstalled on spanking brand new firecudas, it's still there

Build 3.1.4

 

--
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-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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.

[George Nachman]

Let me know what the output of `mount` is. I think I'm going to have to parse it myself to find the stupid network paths.

[Diez Roggisch]

Hi,

Let me know what the output of `mount` is. I think I'm going to have to parse it myself to find the stupid network paths.

For me there sometimes is network mounts, but most of the times not. Currently the mount output is

/dev/disk1 on / (hfs, local, journaled)

devfs on /dev (devfs, local, nobrowse)

map -hosts on /net (autofs, nosuid, automounted, nobrowse)

map auto_home on /home (autofs, automounted, nobrowse)

map -fstab on /Network/Servers (autofs, automounted, nobrowse)

/dev/disk3s2 on /Volumes/standalone-env (hfs, local, nodev, nosuid, journaled, noowners, mounted by dir)

/dev/disk4s1 on /Volumes/boot (msdos, local, nodev, nosuid, noowners, quarantine, mounted by dir)

/dev/disk4s2 on /Volumes/Untitled (ufsd_ExtFS, local, nodev, nosuid, noowners, mounted by dir)

Maybe a speciality: I use ParagonFS to mount EXT4 filesystems (you can see that in the last line)

I’m on vacation for the next two weeks, I will try & instrument the application for you after that.

Cheers,

Diez

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/dKJD1FLGp5Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to iterm2-discus...@googlegroups.com.

[George Nachman]

You can always manually exclude network folders from being accessed by adding them to Prefs > Advanced > Paths to ignore for Semantic History.

Hi,

To unsubscribe from this group and all its topics, send an email to iterm2-discuss+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.