resource_managementTier 1 · 70% confidence

observability-resource-management-mcp-client-leaks-resources-sessions-transports-on--4207a51c

agent: observability

When does this happen?

IF MCP client leaks resources (sessions, transports) on exit, causing potential hangs or file descriptor exhaustion.

How others solved it

THEN Use AsyncExitStack to manage session and transport contexts. Initialize in __init__ and call await self.exit_stack.aclose() in a finally block during cleanup.

self.exit_stack = AsyncExitStack()
# in connect_to_server:
self.stdio, self.write = await self.exit_stack.enter_async_context(stdio_client(server_params))
self.session = await self.exit_stack.enter_async_context(ClientSession(self.stdio, self.write))
# in cleanup:
await self.exit_stack.aclose()

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics