-
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
Dry run memoy error and abort - freeing unallocated pointer #7283
Comments
This is legit, I saw it before but couldn't get to it. Do you want to try to fix it or would you rather wait for someone from the team to do it? The easiest way to pinpoint it (and it should be fairly simple) would be building fluent-bit with address sanitizer. If you decide you want to give it a try but don't know how to let me know and I'll guide you through the process. |
FYI, it doesn't fail on container builds so guessing it's a macOS thing: $ docker run --rm -it fluent/fluent-bit:2.1.1 --dry-run
Fluent Bit v2.1.1
* Copyright (C) 2015-2022 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
configuration test is successful
$ docker run --rm -it fluent/fluent-bit:2.1.2 --dry-run
Fluent Bit v2.1.2
* Copyright (C) 2015-2022 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
configuration test is successful
|
Confirmed that the Linux version does not appear to be affected. I also tested the Docker versions and do not see this error. @leonardo-albertovich I can't promise that this is something I'll have the time to fix myself, but if I do get around to it, I'll post a PR here. If I do take a look, I'll probably ping you for some guidance, so I appreciate the offer. I'm not that familiar with the C ecosystem. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
Haven't got a chance to look at this but I assume it still exists. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
Still an issue as of v2.2.2
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
This issue was closed because it has been stalled for 5 days with no activity. |
Bug Report
Describe the bug
Any call to dry run seems to fail, even when the configuration test is successful. Example using the default configuration:
The dry run feature is non-functional as a result.
Edit: seems to be confined to MacOS - I do not see the issue on Linux versions. I have not tested Windows versions.
To Reproduce
Run the above example using Fluent Bit 2.1.1 on MacOS.
Expected behavior
Fluent Bit should not abort and instead should exit successfully (code 0).
Your Environment
The text was updated successfully, but these errors were encountered: