Joel

@cede87: As I noted in my [comment](https://github.com/fluent/fluentd/issues/1657#issuecomment-321305179) on April 9, 2017 the underlying issue here appears to be in the default Ruby garbage collector and memory allocator. The Fluentd developers...

@cede87: The presence of `libjemalloc.so.2` indicates you might be running jemalloc 5 instead of jemalloc 3. During a discussion about making [jemalloc the default allocator for Ruby](https://bugs.ruby-lang.org/issues/14718#note-59), it was noted:...

This issue should remain open until it is resolved. It has continued to affect people since it was reported in 2017, and the current best workarounds are laborious and invasive.

I repeat: This issue should remain open until it is resolved. It has continued to affect people since it was reported in 2017, and the current best workarounds are laborious...

@ashie: Thank you for looking into this issue and confirming yourself what the community has been reporting. Regarding the efficiency of jemalloc 3.x vs 5.x, the common trend I've read...

Hmm... so when I enter the program with a debugger, `something`'s `value` isn't a `str` or `dict`... it's a `list`. And that made sense to me, since telegram-cli returns a...

@another-rex: Yes, when I test with osv-scanner v2-beta1 running inside a Debian 12 container, it correctly outputs only CVE-2024-13176. However, as you suspected the `--lockfile` option is kind of broken...