On a mac, .zshrc is periodically re-ran

[grbinho]

What happened?

Hi, I'm playing around with supacode and I ran into a potential issue.

I kept it running over night and I woke up to this error on my shells

error starting IO thread: error.SystemResources  The underlying shell or command was unable to be started. This error is usually due to exhausting a system resource. If this looks like a bug, please report it.  This terminal is non-functional. Please close it and try again.

For me this happened because i had an insane amount of ssh-agent processes running.
They are usually started from my zshrc when i start a terminal (Ghostty usually).
I killed all the processes, but they started spawning up again. Killed supacode and silence.
It seems that supacode re-runs zshrc quite often and in my case that ended up exhausting my resources.

Is there a good reason for such behavior?

Steps to reproduce

1. Spawn some process in your zshrc
2. Let supacode run
3. Observer process count grow

Supacode version and build

Version 0.10.8 (1785775286)

macOS version

26.6.1 (25G76)

System locale

en_HR

Mac hardware

M2 Pro

Relevant logs or screenshots

Are you planning to fix this yourself?

• I intend to open a pull request once this is confirmed and marked ready.

Before submitting

• I searched existing issues and this is not a duplicate.
• I am on the latest available version of Supacode.
• I understand pull requests are closed until the issue is marked ready.
• I agree to follow this project's Code of Conduct.

[github-actions]

Thank you for filing this. A maintainer will review it and follow up here.

Please do not start any work or open a pull request until this issue is labeled ready. That label is a maintainer's go-ahead: a pull request opened against an issue that is not yet ready is labeled invalid until then. You will get a comment here the moment it is marked ready.

See CONTRIBUTING.md for the full flow.

[sbertix]

Is there a good reason for such behavior?

This looks like a byproduct of having to source .zshrc for background processes, mainly because few people use .zprofile and we've had several issues opened relating to those $PATH expectations that we can’t meet without it 😢

But yeah, I totally understand this. I’m not really sure how to fix it, though, because “working out of the box” for most users probably outweighs “erroring under heavy loads.” Any suggestions?

[grbinho]

Hi @sbertix thanks for looking into it.

I haven't really look too deeply into it. Seems reasonable to read .zshrc when a console session starts up, but why does it need to be sourced every few seconds? Because it looks like that is what it's being done when observing it from outside. I had only two active console sessions and it resulted in the resource exhaustion over a day maybe.

It's not really blocking me anymore because I removed ssh-agent eval from my .zshrc but it still seems like sourcing it every few seconds should not be necessary.

[sbertix]

There's background process for lots of stuff (one of the tickets was about gh not being resolved, for instance). Latest tip updates should have made it better since most of those are now event-based, but they can't all be unfortunately so we still have things running on a timer and that can definitely choke with many worktrees.
I'm not saying there's no room to improve that (or that we won't), btw, just that it's a conscious trade-off.

[grbinho]

Fair enough. Hopefully this issue gives you some additional context and helps with decisions.