On 31/05/11 03:20, guest01 wrote:
ok, I can at least try to start it under valgrind, which I have never
heard before. Do I just start squid under valgrind and send you the
logfile? Do you need any special options?
Squid need valgrind support built in when this is done.
Apart from that yes it is just run Squid using valgrind like you would a
debugger. Once it gets to some unusual amount of RAM usage shutdown
Squid and send in the resulting valgrind log.
We shall see if anything interesting pops up there.
Thank you
Amos
On Mon, May 30, 2011 at 2:15 PM, Amos Jeffries<squid3@xxxxxxxxxxxxx> wrote:
On 30/05/11 20:07, guest01 wrote:
Hi,
Any news on this topic? Unfortunately, RAM is running full within days
and at the moment, our workaround is to do a reboot ... We would
appreciate any other solution!
thanks,
peter
:) I was just looking at this bug again today.
:( still no seriously good ideas.
Is there any way at all you can run one of these Squid under valgrind and
get a report of what its memory is doing?
Even if valgrind is just built in to squid. The info report gains a lot of
extra memory stats and leak report without having to stop squid running.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.12
Beta testers wanted for 3.2.0.7 and 3.1.12.1
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.12
Beta testers wanted for 3.2.0.7 and 3.1.12.1
