RockteMQ-AI commented on issue #1358: URL: https://github.com/apache/rocketmq-clients/issues/1358#issuecomment-5655082147
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The 13 `lostcancel` findings are real and have two distinct impacts: 1. **Timer/context leaks** (11 unary RPCs + dial): Every call to `context.WithTimeout` without storing the cancel function leaks the timer until the deadline expires. Under high call rates, this accumulates unnecessary pending timers. 2. **Telemetry stream killed periodically**: The per-call timeout on the bidirectional stream causes the cached `clientSettings.observer` to be torn down and rebuilt every `timeout` interval, which is a behavioral bug beyond just a vet warning. The fix is straightforward: store and defer the cancel function in each unary RPC wrapper, and for Telemetry, either remove the per-call timeout or apply it only to the initial dial (not the long-lived stream). --- *Automated evaluation by github-manager* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
