Tristan

Yup; just in case here's the [job](https://gitlab.com/mangadex-pub/haproxy/-/jobs/2568565215) and here's its haproxy -vv output if you want to check that I got the flags right (Notably it's not clear to me...

From other issues, seems like `-ggdb3` is in fact meant to be passed as a cflag; sec imma retry with that...

Interestingly, the logs print this with those builds: 

Since I missed (or rather didn't pass correctly) the `-ggdb3` in the previous, here's a coredump on a build that has it properly Core dump ```plain $ gdb haproxy core...

After moving to the tip of 2.7-dev ([`43c090c`](http://git.haproxy.org/?p=haproxy.git;a=tree;h=9564201454e5b0e5829b92e91b265434e520098b;hb=43c090c1ed9d06100be1e75a87d4e372ba7fee94) built in [this job](https://gitlab.com/mangadex-pub/haproxy/-/jobs/2577449302)) I am indeed not seeing the crash anymore 🎉 Or, at the very least least, things have been...

nevermind, it took a long while (~2.5 hours) but I got another segfault in the logs (unfortunately didn't have coredumps enabled... I'll reenable them and wait a few hours for...

Took about 3h20 and ~740k QUIC requests but it finally happened again! 🥲 That call chain looks to be the culprit https://github.com/haproxy/haproxy/blob/43c090c1ed9d06100be1e75a87d4e372ba7fee94/src/mux_quic.c#L757 https://github.com/haproxy/haproxy/blob/43c090c1ed9d06100be1e75a87d4e372ba7fee94/src/pool.c#L747 One thing I noted before seeing the...

Oh I realize I hadn't given feedback on this issue before and now it unfortunately missed 2.6.2 😅 (if this happens again in this or another issue, do feel free...

Hmmm... Indeed... Now I'm confused too, but I was a bit too quick to read the stack traces as the bug condition seems ever so slightly different... ``` 2022-07-23T07:48:06+01:00 FATAL:...

I believe this issue is fixed, now that 2.6.5 is emitted. Never had any other occurence of it on my end either over the past few weeks of 2.7-dev.