Chris Wittich

> How did you install openssl-1.1.1 with quic, can you provide some details? I wasn't being very clear, sorry. I'm using the quictls OpenSSL fork at https://github.com/quictls/openssl/tree/OpenSSL_1_1_1q+quic as described in...

> if you have a chance, can you try 3.0.5 ? That doesn't seem to cause any noticeable change. It still crashes with `FATAL: bug condition "offset >= qcs->tx.offset" matched...

> You must absolutely not use a process in such a state, it is guaranteed that bad stuff will happen. Thank you for the warning! I have now changed the...

Here my observations made with 2.7-dev2-48bb8759086: * Without specifying a quic-cc-algo option the process ran for about 2 hours while increasing its allocated pool mem, then segfaulted: ``` "2022-08-04T11:01:07.869Z","[WARNING] (1)...

I didn't encounter any more crashes/ALERTs since yesterday with 2.7-dev2-48bb8759086 / quictls 3.0.5 / quic-cc-algo newreno, but mem utilization keeps on rising (now at 330MB, previous max without quic was...

Just FYI, I did a quick test today with 2.7-dev3-35a66c0a367e and the situation seems unchanged from what I experienced before

I haven't had time to follow up on this issue lately, sorry about that. The assertion failure `offset >= qcs->tx.offset` still remains on 2.6.4, so I gave the dev branch...

> Please also consider using -O1 compilation option in place of -O2 to have more chance to get useful information from the backtrace. This gdb command would also give us...

> You will be able to access the traces from the backing-file even after haproxy has crashed. I have generated the trace file. How can I extract the relevant information...

> Compress the file and attach the result to this issue please. see attached file (it's a 7z archive actually) [buf1.zip](https://github.com/haproxy/haproxy/files/9491937/buf1.zip)