I tried to recreate this problem, but no luck so far... is there any particular type of request that I need to use to trigger the memory leak? I just ran a few hundred thousand requests for the same 1KB file through 2.0.41-pre2 with the mod_mem_cache settings below, and I can't see any sign of memory growth in the httpd yet.
Thanks, Brian On Tue, 2002-09-10 at 14:40, Jean-Jacques Clar wrote: > I guess my leak is from a different source. > Refreshing files in mod_mem_cache drive up the allocated memory in > aprlib. > It is consistent and has been there since I started using mod_cache > (3-4 months ago). > > Justin, > Were you using caching modules when you were able to reproduce/fix > Brad's leak? > What did you do to reproduce it on your Unix box? > Could you please try the same settings using mem cache? > Here is my config: > > LoadModule cache_module modules/mod_cach.nlm > <IfModule mod_cache.c> > CacheMaxExpire 60 > CacheDefaultExpire 12000000 > CacheIgnoreCacheControl On > # LoadModule disk_cache_module modules/dsk_cach.nlm > <IfModule mod_disk_cache.c> > CacheRoot sys:/cacheroot > CacheSize 256 > CacheEnable disk / > CacheDirLevels 6 > CacheDirLength 3 > </IfModule> > LoadModule mem_cache_module modules/mem_cach.nlm > <IfModule mod_mem_cache.c> > CacheEnable mem / > MCacheSize 70000 > MCacheMaxObjectCount 13001 > MCacheMinObjectSize 1 > MCacheMaxObjectSize 690000 > </IfModule> > </IfModule> > > Thanks, > > Jean-Jacques > > >>> [EMAIL PROTECTED] 09/10/02 02:25PM >>> > On Mon, Sep 09, 2002 at 02:41:33PM -0600, Brad Nicholes wrote: > > Has anybody else noticed a memory leak when requesting pages > less > > than 8k? If I repeatedly request pages less than 8k I have noticed > > that > > Yeah, my recent commit to core_output_filter seems to have fixed > this for me. > > We removed the EOS buckets from the brigade, but we never deleted > them. In order to be cleaned up with the pool, they have to be > in a brigade. An orphan bucket won't be freed. -- justin