the cause is either a fiber deadlock, or an incorrectly unreferenced/canceled watcher

[sxllllll]

I found that when using http-client, an error will be thrown if the request times out. It is easy to cause deadlock, causing the memory to increase. Has anyone encountered this problem?

Why 😫

Exception1：
Uncaught AssertionError thrown in event loop callback Amp\Http\Client\Connection\Internal\Http2ConnectionProcessor::Amp\Http\Client\Connection\Internal\{closure} defined in /var/www/hiwaifu_php/vendor/amphp/http-client/src/Connection/Internal/Http2ConnectionProcessor.php:1580; use Revolt\EventLoop::setErrorHandler() to gracefully handle such exceptions: Stream watcher invoked after stream closed

Exception2:
Event loop terminated without resuming the current suspension (the cause is either a fiber deadlock, or an incorrectly unreferenced/canceled watcher):

[sxllllll]

http-client version :

[kelunik]

Do you have a fully runnable reproduction case? Could you also please share the stack traces?

[trowski]

Can you please try your code again with amphp/pipeline@1.2.3. A regression in 1.2.2 may not have been throwing an exception when it should have, instead leaving the coroutine to hang, so that may have been the cause here.