From owner-freebsd-questions@FreeBSD.ORG  Thu Sep 25 10:54:40 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D6D4A98F
 for <freebsd-questions@freebsd.org>; Thu, 25 Sep 2014 10:54:40 +0000 (UTC)
Received: from btw.pki2.com (btw.pki2.com [IPv6:2001:470:a:6fd::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9F0CD9A5
 for <freebsd-questions@freebsd.org>; Thu, 25 Sep 2014 10:54:40 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
 by btw.pki2.com (8.14.9/8.14.9) with ESMTP id s8PAsSfP090760;
 Thu, 25 Sep 2014 03:54:29 -0700 (PDT)
 (envelope-from freebsd@pki2.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=pki2.com; s=pki2;
 t=1411642469; bh=rtcHOnvLXzRx4286J315sPsFWFqqwsjkCUksCEwY7pQ=;
 h=Subject:From:To:Cc:In-Reply-To:References:Date;
 b=uH8LGEF9ZpUbfjWj96qY5gYajeUWGOYixkNpV8+lpUurLi1s0b30D2wwkxqOJb9YS
 sMT0cAc5/rBGRFGHT/yLjEvCrx/nPDP7w9ORu1SoTZwXafFDu1cnlvAra6CiqAwzSC
 ESnuG0Ou4Bkkacx4jpRdoajeGl0GPVKM8NyEEuygAFhXQCuLBKKC80fv5DYsXQgi51
 o1VaTYhS8f44bThssNEk7R7r2EbWgymTLJuczpDclPrkeeCWEULJs3+IG9qtssnJHd
 hxFtl3tsxNCjDXPWHxJb3R1MafyKQW/slK/8cxUr1NIlOFegfnccASmHkDTQ3+8xLE
 ZL8jAu50CTjEw==
Subject: Re: squid-3.4.8_1 leaking memory
From: Dennis Glatting <freebsd@pki2.com>
To: Victor Sudakov <vas@mpeks.tomsk.su>
In-Reply-To: <20140925045657.GA71070@admin.sibptus.tomsk.ru>
References: <20140925045657.GA71070@admin.sibptus.tomsk.ru>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Thu, 25 Sep 2014 03:54:28 -0700
Message-ID: <1411642468.3895.847.camel@btw.pki2.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
X-SoftwareMunitions-MailScanner-Information: Dennis Glatting
X-SoftwareMunitions-MailScanner-ID: s8PAsSfP090760
X-SoftwareMunitions-MailScanner: Found to be clean
X-MailScanner-From: freebsd@pki2.com
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Sep 2014 10:54:40 -0000

On Thu, 2014-09-25 at 11:56 +0700, Victor Sudakov wrote:
> Colleagues,
> 
> squid-3.4.8_1 seems to be leaking memory heavily. Its SIZE and RES are
> growing several MB per minute until eventually swapping begins.
> 
> Is anyone using it? Have you encountered this problem?
> 
> The relevant entries in squid.conf are:
> 
> cache_mem 128 MB
> cache_dir ufs /webcache/cache 512 16 256
> memory_pools off # neither "on" nor "off" have any effect on leaking.
> 
> As you see, the memory requirements should be rather modest.
> 
> Running on 8.4-RELEASE-p16 i386.
> 

The Squid Cache web site DOES NOT list 3.4.8 as the stable release,
rather 3.4.7 is listed as the stable release. There are also 18 change
sets listed for 3.4.7 and three for 3.4.8.

I did not follow the thread where we went from 3.4.7 to 3.4.8.