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
Segmentation fault after updating from version 1.16.3 to 1.16.4 #378
Comments
Customize Dockerfile like this:
Then build image, use custom build may cause SEGV.
|
Workaround: disable jemalloc in customized container image. Set empty LD_PRELOAD="".
|
MEMO: It seems that it was crashed here: def self.read_and_free_outstr(ptr)
str = ptr.read_string
LibC.free(ptr)
str
end LibC.free is called via read_and_free_outstr in def cursor
out_ptr = FFI::MemoryPointer.new(:pointer, 1)
if (rc = Native.sd_journal_get_cursor(@ptr, out_ptr)) < 0
raise JournalError, rc
end
Journal.read_and_free_outstr(out_ptr.read_pointer)
end It was assumed that out_ptr is allocated and should be freed. With jemalloc, this mechanism may not work as expected. |
would it make sense to open a bug report on ledbettj systemd-journal project? |
Describe the bug
After updating the official docker container from fluent/fluentd:v1.16.3 to fluent/fluentd:v1.16.4 I got a segmentation fault during startup which end in a endless starting loop.
Additionally I have the following gem modules installed
To Reproduce
just update and restart
Expected behavior
should not crash
Your Environment
Your Configuration
Your Error Log
Additional context
No response
The text was updated successfully, but these errors were encountered: