[P1] Avoid pausing services while references remain
In release the service is paused unconditionally (entry.service.pause() on lines 93‑101). When multiple clients acquire the same service, the first release call sets the pause event even though refcount is still >0, temporarily stopping the service for the remaining user until another resume happens. The prior implementation only paused when the reference count hit zero. This change can stall shared services unexpectedly; the pause should occur only when refcount drops to zero.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #3332 (comment)
[P1] Avoid pausing services while references remain
In
releasethe service is paused unconditionally (entry.service.pause()on lines 93‑101). When multiple clients acquire the same service, the first release call sets the pause event even thoughrefcountis still >0, temporarily stopping the service for the remaining user until anotherresumehappens. The prior implementation only paused when the reference count hit zero. This change can stall shared services unexpectedly; the pause should occur only whenrefcountdrops to zero.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #3332 (comment)