SIGABRT and Segfault in _S_create_c_locale #3586
-
I'm not sure yet if it's reproducible. Tenzir version: ~4.2 (I don't find a command or flag to get the exact version)
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
You can do this with Let's take a look at the stacktrace. There isn't much to see here because it's from an optimized binary, so let me try to explain bottom-up what can be seen:
We use This deletion handler is marked noexcept, and we appear to throw an exception in it, which causes the program to terminate by calling The exception seems to be coming from a call to
Here it looks like we are formatting the output of My best guess is that we have some call to If you can reproduce this (somewhat) reliably then it should be easy to find the source of this runtime error and to fix it. |
Beta Was this translation helpful? Give feedback.
-
Version (sorry for the limited research previously):
I managed to reproduce reliably, will reach out via Discord for the file (but it's not urgent problem on my side). |
Beta Was this translation helpful? Give feedback.
-
I got the file you shared with me—thanks!—and used this build, which is current main as of writing this message:
I used this pipeline:
The release build ran through; since we also discussed performance relating to this input in Discord, here's the relevant portion of the metrics:
The performance for this is oddly low despite the batching being near optimal. We definitely need to look into that further as 16k EPS is a lot lower than what we see for other events, and it's not even of a particularly complex shape. Since that had not crashed for me I tried again with the debug build. That was a lot slower (as expected), but it did not crash for me either. I then tried to build 7500759 specifically, but that did also not crash for either a release or a debug build on my end. I will try again tomorrow with a Docker build of this specific commit. |
Beta Was this translation helpful? Give feedback.
-
@netantho the exception message in your backtrace indicates an issue with the locale, this is hard to investigate without the specific Dockerfile and build invocation that you used. There may still be a potential workaround that you could try: Add
|
Beta Was this translation helpful? Give feedback.
-
After more thorough testing:
I've been unsuccessful with a docker container. Here's what I've tried so far:
|
Beta Was this translation helpful? Give feedback.
-
I created a fix for the problem at #3593. |
Beta Was this translation helpful? Give feedback.
I created a fix for the problem at #3593.