You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Go harness leaks gRPC connections and can deadlock when closing streams #40260
We run Prism in a long-lived worker process where each job starts its own go harness in that process.
The problem is that the harness caches Data and State gRPC streams on DataChannelManager / StateChannelManager and never closes them so the streams and their read goroutines stay. Over many jobs the process accumulates connections and goroutines until it is unusable.
In addition to that, there is another problem that shows up on a long-lived process when the harness sends output to the runner on a stream that another goroutine is already reading. If the runner has closed that stream, the send fails with EOF and then tries to read too, and those two reads deadlock.
Activity
igor-dv commentedon Sep 24, 2026
.take-issue