On 11/01/11 09:47, John Craws wrote:
Hi,
I just did a few tests using 3.1.10 and the issue appears to be fixed.
I browsed the changelog but could not find something that seemed to be
directly related. Is it a side effect of another fix? If so, which
one?
I'll keep testing, but it's promising.
Thanks a lot,
John Craws
That sounds like a side effect of the bug 3113 and 3096 fixes. Between
them they limit the amount of RAM Squid uses for in-transit requests and
release the individual I/O blocks immediately.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.10
Beta testers wanted for 3.2.0.4
