-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Deadlocks at the latest version #1201
Comments
Same situation
|
Can we have other threads stack in order to understand where the deadlock occurs ? |
can we have more information about other thread stacks ? Did you try the lates v1.8.1 version ? We have solved a few race condition here and there. |
I think I can reproduce this with a test case in the Shopify/ghostferry repo (but it requires ruby to run). Here's the goroutine stacks from debug/pprof (the line number in ghostferry may not match up with what's in the repo as i have a working copy locally):
|
@shuhaowu I'm not sure you are facing a deadlock rather than a thread locked in I/O. |
@DGSV you are possibly right. We somehow fixed this issue without patching logrus. To be honest I don't remember what has leaded us to the solution :( |
seeing deadlock with version "github.com/sirupsen/logrus v1.8.1" |
@andreish can we have stack trace ? otherwise we can't help there. A reproducible test case would help too. |
Hi, looking more in depth found that the problem is mainly caused by using a custom output on standard logger , then inside the function that writes the output the standard logger is called to log some info ... probably not the correct use case . (the test code that is close to my case is here: https://github.com/andreish/logrus/blob/master/issue_1201_test.go ) |
Same here, version is
Can't provide minimal reproduceable app, but it happens a lot in production app |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Hi. We are using logger to log http-request in particular, we have simple middleware, which logs start and the end of request:
But after some point we are getting tons of hanging goroutines which cause application deaklock (we cannot accept new http-requests):
I am currently clueless. I guess it's something related to #1131 (but it's reverted), maybe not.
The text was updated successfully, but these errors were encountered: