-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Coroutine deadlock occurs after killing the process #5663
Comments
I can't reproduce this issue. Please share your database.php file or check if the database username and password are correct. |
Please show your php extension list. |
I can't share my database. All I can say is that the database is accessible. About PHP extension:
|
@NathanFreeman I think hyperf has many problems, which may not be swoole's problem. |
Could you please show me your server.php? |
It looks like PHP has thrown an exception. Is there a complete log output? |
The idea you put forward is possible, which may be related to the number of connections to the database, but now I can't connect to the database of the intranet. It doesn't have a vpn channel, so I can't locate it now. Thank you for your idea. I will debug it in the next two days. Please don't close the issue. Thank you. |
This occurs because the framework fails to fully clean up coroutines that are currently running when it exits, such as certain monitors or connection pool managers. If you confirm that the leaking coroutines are not performing uninterruptible transactions, you can disregard this warning. |
The text was updated successfully, but these errors were encountered: