On Wed, Aug 20, 2025 at 03:58:32PM +0200, Amaury Denoyelle wrote: > On Fri, Aug 15, 2025 at 03:33:10PM +0300, Luke Seelenbinder wrote: > > Hi all, > > We've just isolated a very consistent way to recreate this (or similar > > conditions) in 3.2.4. > > If you reload HAProxy and then use an already established QUIC connection, > > the following occurs consistently on the previous worker process: > > haproxy[1464934]: FATAL: bug condition "((&qcs->el_buf)->n != > > (&qcs->el_buf))" matched at src/mux_quic.c:3738 > > [...] > Thanks for the report. A similar issue was also opened on github also > related to reload. I have probably missed something here. I did not have > time recently to work on this, but I'm planning to look at this soon. > I'll let you know if I need anything or if I'm able to produce a fix.
I have pushed yesterday a fix which should resolve reload operation used in conjunction with QUIC emission. Here is the ID of the relevant commit. commit dcf22616123432e3230c0a084cf13c5adc57b851 BUG/MAJOR: mux-quic: fix crash on reload during emission This is scheduled for backport up to 3.0. If you want you can also apply on top of your haproxy repository, the patch is quite small. Regards, -- Amaury Denoyelle
