Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
sxllllll opened this issue Feb 27, 2025 · 2 comments

Comments

@sxllllll
Copy link

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 😫

Image

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):

Image

Image

@sxllllll
Copy link
Author

http-client version :

Image

@kelunik
Copy link
Member

kelunik commented Feb 27, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants