segfault caused by out_stdout about fluent-bit HOT 8 CLOSED

On the other hand, segfault is not happened when output is out_null.

It is not right. Segfault also occurs when output plugin is out_null.

from fluent-bit.

Thanks for the report. I was able to reproduce it, will do some troubleshooting late today.

from fluent-bit.

root cause: when the thread is destroyed, it was not decrementing the task->users count, so the task always remain and generated conflicts.

from fluent-bit.

@nokute78 I will keep this ticket open until final confirmation.

from fluent-bit.

@edsiper Thank you for fixing!
The issue is fixed with 08c71aa in my environment.

from fluent-bit.

Awesome :)

from fluent-bit.

for the record.. about:

(By the way, Default log level is debug in that commit. Is it intentional?)

no, it was the pending implementation for 'logging worker support' into the main thread. Now it's fixed in master by 14f5eb0

from fluent-bit.

Thanks!
Default log level is fixed.

from fluent-bit.