[squid-users] Significant memory leak with version 5.x (not with 4.17)

[Alex Rousskov]

On 1/13/22 10:37 AM, Loučanský Lukáš wrote:

> I'd like to ask if I'm doing anything wrong. Am I correct when I
> think, that patch #957 is not backported/merged to tunnel.cc for v5.3
> at the git repo v5 branch?

You are correct -- the fix is not in v5 (yet). I cannot speak for Amos,
and the Project does not have a good way to request/track backporting
requests yet, but I bet that #957 fix (or its equivalent) will
eventually be added to v5. Properly evaluating/testing/backporting
changes takes time and effort.


> As there is a "small" warning not to use v6 in production - I'd like
> to ask if is it wise to modify tunnel.cc file like I did it in my
> current 5.3-20211214-r832aa256c. Or it would be better to switch to
> git master branch.

Due to other v5 bugs, it is currently impractical to run unpatched v5 in
many production environments. Many still run v4. Some prefer to risk
patching v5 than to risk running master/v6. Few make the opposite choice
(often because they need a new master/v6-only feature). It is impossible
to give a correct one-size-fits-all advice here: YMMV.


> But FYI I had a compilation error due -wshadow option:
> 
> XactionRep.cc:174:20: error: declaration of ‘String name’ shadows a parameter [-Werror=shadow]
> XactionRep.cc:486:33: error: declaration of ‘services’ shadows a previous local [-Werror=shadow]

Fixed at https://github.com/squid-cache/squid/pull/962


HTH,

Alex.