secretive icon indicating copy to clipboard operation
secretive copied to clipboard

SecretAgent deadlocked after Sonoma 14.4.1 upgrade

Open mischaelschill opened this issue 2 years ago • 19 comments

After upgrading to Sonoma 14.4.1 (skipping 14.4.0), the SecretAgent is locking up regularly. The symptom is ssh blocking indefinitely while waiting for the SecretAgent. If the SecretAgent is killed (e.g. by pkill SecretAgent), ssh works fine for a little while. Unfortunately, I do not know where to look for the log file of the SecretAgent.

mischaelschill avatar Apr 18 '24 08:04 mischaelschill

I'm not aware of any known issues on 14.4.1 (that's what I'm using) – can you take a sample of SecretAgent next time this happens? Open Activity Manager and select "Sample Process" here: image

maxgoedjen avatar Apr 19 '24 04:04 maxgoedjen

Sample of SecretAgent.txt

Here is mine.

3apa3a-b-ta3e avatar Apr 22 '24 12:04 3apa3a-b-ta3e

I also have this on macOS 14.5

lenovouser avatar May 26 '24 12:05 lenovouser

Same here, since yesterday it started to consume a lot of CPU for the initial SSH connection while also taking several seconds to complete.

I am running macOS 14.5 since around 10 days & build 2.4.1 since months, but it started to get slow yesterday.

bicrypt avatar May 26 '24 12:05 bicrypt

Just to add — it happens more frequently when there is a VSCode opened and doing background repo refresh. Which hasn't been an issue with previous macOS/Secretive versions.

3apa3a-b-ta3e avatar May 29 '24 08:05 3apa3a-b-ta3e

I am seeing this issue as well. When logging in, there's a STORM of messages seen in "log stream", but apparently unrelated to Secretive itself. I think it's actually caused by iTerm, it doesn't happen in Terminal (but there are many differences between those two when it comes to sessions and stuff, so it isnt' fair to outright blame iTerm). But since that't the only thing I regularly update (running nightly build), I think it points to that.

zviratko avatar May 31 '24 09:05 zviratko

Ok, I'm more ready to blame iTerm now :) Apparently 3.5.0 came out May 17th. As I'm running nightly I didn't really notice anything. Downgrading to 3.4.23 fixes the issue, upgrading to 3.5.0 brings it back. I'm not sure how long I had this issue without noticing, but it can't be that long, I also skipped a few nightlies so it could be 2 weeks. Something just before the release broke it.

zviratko avatar May 31 '24 10:05 zviratko

https://gitlab.com/gnachman/iterm2/-/issues/11483

zviratko avatar May 31 '24 10:05 zviratko

The issue persists, and I'm not using iTerm. It is not a delay, the process is stuck until killed. I now have a job which kills the process every 10 Minutes which alleviates the problem.

mischaelschill avatar May 31 '24 15:05 mischaelschill

I think that's a separate issue. I see high CPU usage and delay when the agent is signing.

zviratko avatar May 31 '24 17:05 zviratko

iterm 3.5.1 resolves the issue for me

slimm609 avatar Jun 12 '24 14:06 slimm609

Likewise! It's like night and day.

Manouchehri avatar Jun 12 '24 15:06 Manouchehri

Still facing the issue even not having iTerm installed. I also have Visual Studio, Intellij and Warp.

rfscouto avatar Jun 13 '24 07:06 rfscouto

Any news? I'm still affected on 14.5

mischaelschill avatar Aug 08 '24 12:08 mischaelschill

same here

rfscouto avatar Aug 11 '24 10:08 rfscouto

Also have this on 14.7 (23H124), no iTerm.

zeha avatar Sep 23 '24 16:09 zeha

I have a consistent repro for this.

  1. ssh-add -l, responses return immediately because SecretAgent is responsive.
  2. In a background terminal, run nc -U $SSH_AUTH_SOCK.
  3. ssh-add -l, hangs, SecretAgent is not responsive.
  4. Kill the netcat, the hung ssh-add will return results immediately.

I can't be sure that this is the same hang that VSCode produces, but hopefully it can help to debug. This repro works for me on macOS 12.7.1 (21G920), with Secretive Version 2.4.1 (1.7648958148).

CGamesPlay avatar Oct 09 '24 03:10 CGamesPlay

Any updates on this? Almost everytime I want to fetch, push or pull some changes in git, I have to force quit the SecretAgent in order to restart it, as otherwise it would hang indefinitely.

julian-baumann avatar Jan 08 '25 15:01 julian-baumann