Assuming it is the pixmaps being cached by firefox causing this growth, can someone with this problem please see this thread: http://forums.mozillazine.org/viewtopic.php?t=354828#memcache And set the maximum memory cache to 8000 or 16000, then see if this problem persists? The quick way to do this is: about:config Create a new integer key, named "browser.cache.memory.capacity" and assign a value in KB for the cache size. You can confirm the size set by opening: about:cache You should see: Maximum storage size: 16000 KiB (or whatever you set it to). Watching xrestop, the Pxm mem value for Firefox should not exceed your maximum set. If it remains below your value, but you still see X.org or Firefox consuming/leaking memory, it may be an entirely different problem, but I suspect this will fix the problem. Josh On 2/1/06, Matt Reimer <mattjreimer_at_gmail.com> wrote: > On 2/1/06, Randy Bush <randy_at_psg.com> wrote: > > > I've been running Xorg, firefox, and emacs, since last night (with > > > jemalloc's redzone code enabled) on a two-day-old -current build, and > > > after many invocations of firefox and emacs, with serious attempts to > > > make firefox use lots of memory, Xorg's, memory usage has stabilized > > > at ~75 MB mapped, and ~35 MB resident. > > > > what seems to be common with those of us seeing leakage is multiple > > windows and many tabs. i standardly have three windows each with > > six to ten tabs. > > Maybe what's eating up the memory is Firefox 1.5's new feature to > cache extra data in RAM in order to make Back/Forward fast. > > Matt > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Wed Feb 01 2006 - 22:34:46 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:51 UTC