Hanging after unspecified delay when working in Volume in iTerm2 3.1.3-beta1 on macOS High Sierra

Thanks for filing an issue! Please answer the questions below so I can help you.

• iTerm2 version: 3.1.3-beta

• OS version: High Sierra

• Attach here (drag-drop from finder into this window) com.googlecode.iterm2.plist

• Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog

• Are you reporting a performance issue or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample Sample_of_iTerm2.txt

• Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs

Detailed steps to reproduce the problem:

1. Upgrade to High Sierra
2. Open iTerm2
3. Any activities for > 10 minutes (specifically within APFS case-sensitive mounted volume)
4. After hang, force close through Activity Monitor
5. Observe than upon reopening iTerm2, it crashes instantly, and requires reboot to restore functionality.

What happened: iTerm2 hangs and never recovers.

What should have happened: Not hanging.

Do you have any network mounts on this machine? This is the second report of proc_pidinfo hanging.

Does lsof also hang?

It's also possible that proc_pidinfo is not reentrant since I see it in two threads. That would be kind of surprising, though.

Commit 86e1d97c synchronizes access to proc_pidinfo. Please test tomorrow's nightly build and let me know if it helps.

lsof also hangs indeed. No network mounts. Will certainly test and report back!

Same happening to me.

I've pinned it down to htop running for some time before the crash. Any chance you run htop too? Long shot, but worth trying.

@gfiorav I'm always running htop, yes. Might be onto something there. Going to run without opening htop and see if that behaves normally? Is that your experience?

@azide0x37 Yes, exactly that. Refrain from running it and see if it stops from crashing. In my experience it does. Long shot theory: something with Apple's new AFS filesystem is breaking some hack htop (or maybe even top) uses. Please report back!

@azide0x37 I'd like to file a bug report on this issue with Apple. Does lsof hang if you're not using htop? Do you have any network-mounted filesystems?

changed milestone to %Next Beta

No mounted filesystems. Can run lsof without htop (also works alongside, until the point at which we get an iTerm hang.)

Commit d2786790 ensures it will eventually return.

I would like to file a bug against Apple for this, since it looks like a kernel bug. In order to do so, I need a sysdiagnose file. Next time this happens, press Command + Option + Shift + Control + Period. A sysdiagnose process will begin, which can take up to 10 minutes. Once it's done, /private/var/tmp/ will have a file whose name begins with sysdiagnose_. Please attach that to this issue.

Note: when it finishes, a finder window will open to the folder that has the sysdiagnose file.