[squid-users] Squid for Windows: negotiate_kerberos_auth helper seems to leak(?) handles

[Klaus Westkamp]

Hi,

i'm uncertain, wether this mailing list is the correct one to ask, but i 
have the disputable honor to make a squid running on a Windows Server 
(if possible). Whilst squid.exe seems to run fine, i constantly run into 
an unresponsive system, when i enable Kerberos authentication via 
auth_param and the negotiate_kerberos_auth.exe helper.

For a while authentication works fine, but all at the sudden the system 
hangs at 100% CPU usage. My Observation is that one of the 
negotiate_kerberos_auth.exe processes has a constantly increasing number 
of handles (Files and events). If i understand the Sysinternals handle 
tool correctly, most handles are event corrolated.

The setting:

Windows 2012 R2 AD Controllers with Windows 2008R2 Domain Level. A 
Windows Server 2016 running Squid 3.5 for Windows. The squid server is a 
VM running on HyperV with 8 Gigs of RAM and 4 vCPUs. The AD Controllers 
are HP Systems with 24 Cores and 64 GByte of RAM.

Any Suggestions, besides changing to Linux, as inn that case the 
customer will favor to look for another proxy,(Sigh) that i might follow.


Best Regards,

Klaus Westkamp