On Wed, Oct 1, 2008 at 2:47 PM, Ben Collins-Sussman <[EMAIL PROTECTED]> wrote:
>> 2) It seems like many of the people, at least on Windows, can >> reproduce this problem quickly. Could this just be due to running >> requests which create/destroy a lot of memory? > > Definitely. A single checkout causes zillions of subpools to be > repeatedly created and destroyed. Just look at all the looping > constructs in libsvn_fs! > > If you run apache in prefork mode, you won't see this problem -- no > apache process lasts very long. > > If you run apache in threaded (mpm) mode, the apache process runs > forever, and the leak becomes obvious. That's not entirely accurate. Many of the threaded MPMs (i.e. Worker) use multiple subprocesses with multiple threads each, and restart each subprocess periodically. The configuration used at Google happens to limit it to one subprocess with many threads, and doesn't restart it periodically, but that's not the default configuration IIRC. -garrett
