Wow! Yes, I can confirm that a crash does not occur now. :) I checked 2.0 and 2.2 branches. I'll keep testing it for a couple days just to be sure.
So that stacktrace I shared before (on spoe_release_appctx function) was very lucky... Do you think that it'd be possible to find the bug without the replication procedure? Christopher & Willy many thanks for your hard work! I'm always impressed how fast you're able to narrow the bug when you finally get proper input from a reporter. :) wt., 10 lis 2020 o 22:30 Willy Tarreau <w...@1wt.eu> napisał(a): > Hi Christopher, > > On Tue, Nov 10, 2020 at 09:17:15PM +0100, Christopher Faulet wrote: > > Le 10/11/2020 à 18:12, Maciej Zdeb a écrit : > > > Hi, > > > > > > I'm so happy you're able to replicate it! :) > > > > > > With that patch that disabled pool_flush I still can reproduce on my > r&d > > > server and on production, just different places of crash: > > > > > > > Hi Maciej, > > > > Could you test the following patch please ? For now I don't know if it > fully > > fixes the bug. But it is step forward. I must do a deeper review to be > sure > > it covers all cases. > > Looks like you got it right this time, not only it doesn't crash anymore > in my tests, the suspiciously wrong cur_fap that were going negative very > quickly do not happen anymore either! This is a very good news! Looking > forward to read about Maciej's tests. > > Cheers, > Willy >
