Exceptions not handled properly in the proxy's AsyncTunnelHTTPConnection leading to the leaks and pool starvation #1023

Activity

1. rail-chamidullin-myriad commented on Dec 12, 2025

   

   rail-chamidullin-myriad

   on Dec 12, 2025

   More actions

   @janosik47 I am dealing exactly with the same issue and I got to the same conclusion as you. Any update on this? Is there some PR with the fix?
2. janwijbrand commented on Apr 9, 2026

   

   janwijbrand

   on Apr 9, 2026

   More actions

   FWIW to move forward on this issue, I opted for a monkey patch in my code base. Hopefully only temporary. The monkey patch looks more or less like this:

   _original_handle_async_request = AsyncTunnelHTTPConnection.handle_async_request
   
   @functools.wraps(_original_handle_async_request)
   async def _patched_handle_async_request(self, request):
       """Wrapper around ``handle_async_request`` that cleans up the inner
       connection when a tunnel setup error (e.g. TLS handshake failure)
       leaves it as a zombie.
       """
       try:
           return await _original_handle_async_request(self, request)
       except BaseException:
           if not self._connected and not self._connection.is_closed():
               with AsyncShieldCancellation():
                   await self._connection.aclose()
           raise
   
   def apply():
       if (
           AsyncTunnelHTTPConnection.handle_async_request
           is not _patched_handle_async_request
       ):
           AsyncTunnelHTTPConnection.handle_async_request = (
               _patched_handle_async_request
           )