-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Segfault randomly happens with in_health #135
Comments
thanks for catching this. Fixed now (applying fix to 0.9 branch too) |
edsiper
added a commit
that referenced
this issue
Nov 18, 2016
The current input plugins when running in a co-routine, was doing a wrong thread deletion, instead of delete the thread associated with a specific ID, it was deleting 'all threads contexts', leading to a segfault when using in_health plugin. This patch let the input thread deletion just focus on the thread associated to the given id. Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
edsiper
added a commit
that referenced
this issue
Nov 21, 2016
The current input plugins when running in a co-routine, was doing a wrong thread deletion, instead of delete the thread associated with a specific ID, it was deleting 'all threads contexts', leading to a segfault when using in_health plugin. This patch let the input thread deletion just focus on the thread associated to the given id. Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
rawahars
pushed a commit
to rawahars/fluent-bit
that referenced
this issue
Oct 24, 2022
…ent#135) Signed-off-by: Eduardo Silva <eduardo@treasure-data.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to reproduce
Note
Segfault is randomly happened.
However it seems to be happen after outputting this log and it's id >= 2.
Log
The text was updated successfully, but these errors were encountered: