Open Tristan971 opened 5 months ago
Weird variables values: tls_ctx = 0x1 at line 1418 (src/quic_rx.c) after qc_select_tls_ctx() returned.
I have a bunch more of these, and they happen in all LBs with this build, so it has to be something relatively likely to happen and not related to some local network fault or similar.
Most variables are optimized out, so it's difficult to draw any conclusion for this backtrace for the moment. If the crash happens often enough, could it be possible to activate quic
traces please ?
According to the two dumps, this is same bug but at different steps. First dump is during the handshake, and the second one after the handshake. Cannot tell very much more as everything is optimized. Some traces should help.
It is every 2-3 hours or so, depending on the loadbalancer, so I can certainly get traces somewhere with relatively low traffic (or if all the recent trace perf. improvements fix the CPU use on my end).
Either way, I'll get traces for you sometime tomorrow 👍
And there you go, I have 2x core + traces, which happened with only 2 or 3 seconds of interval (after 30 minutes or so of uptime).
Interestingly, the stacktraces are quite different (the second looks like a bug inside the traces code), but maybe they're related.
Detailed Description of the Problem
Well that's a new one. Must be somewhere between 7217a9e and 983513d
Expected Behavior
No crash
Steps to Reproduce the Behavior
?
Do you have any idea what may have caused this?
No response
Do you have an idea how to solve the issue?
No response
What is your configuration?
Output of
haproxy -vv
Last Outputs and Backtraces
Additional Information
No response