On 10.02.2022 18:25, Peter Müller wrote:
> Hello Matthias,

Hi Peter, hi ALL,

I did it the easy way... ;-)

I decided to publish the update to v5.4 and the huge (important!?) patch
which followed a day later in two separate patches.

I tested both of them and found no seen problems. No crashes no
'exceptions'.

Running here under Core163 / 64bit.

Best,
Matthias

> hello *,
> 
> by coincidence, I just stumbled across a Squid 5.4 source tarball on source.ipfire.org:
> 
>> pmueller(a)people01:~$ ls -lah /pub/sources/source-2.x/squid-5.*
>> -rw-r--r-- 1 mfischer people 2.5M Aug  2  2021 /pub/sources/source-2.x/squid-5.1.tar.xz
>> -rw-r--r-- 1 mlorenz  people 2.5M Oct  6 07:44 /pub/sources/source-2.x/squid-5.2.tar.xz
>> -rw-r--r-- 1 mfischer people 2.5M Dec  7 18:42 /pub/sources/source-2.x/squid-5.3.tar.xz
>> -rw-r--r-- 1 mfischer people 2.5M Feb  7 17:10 /pub/sources/source-2.x/squid-5.4.tar.xz
> 
> I therefore presume you are working on this one. :-)

> While Squid 5.2, as it is now present in the upcoming Core Update 164, works fine, I
> observed at least one memory leak in it that eventually caused swapping on a productive
> infrastructure (under high load). Squid 5.4 should have that fixed.
> 
> Because of this, I'd like to have Squid 5.4 in Core Update 164, so our users won't have
> to suffer from this bug. It is good to see you are taking care of it. Please do not feel
> pressured in any way, I just thought I mention this to you. :-)
> 
> Thanks in advance for your efforts, and best regards,
> Peter Müller