On Wed, Jun 22, 2005 at 09:16:31PM +1000, Tim Connors wrote: > On Wed, 22 Jun 2005, Benedek Frank wrote: > > > On Wednesday 22 June 2005 11:36, you wrote: > > > All those other k* programs are just useless helper apps to kde. Blow kde > > > away, and that'll free up a bit. > > > > I have realized that. Actually, having the machine rebootet, with KDM and KDE > > taken out of auto-start, I got a much prettier picture, and a responsive > > system. ALready half-success. When I dont start this kmail prog, I have 140MB > > free mem. Yes, more than half of what I have. Firefox eats up 20 or so. I > > Firefox has a hideous memory leak, where is simply does not decrease > memory usage after you close tabs, or move onto new pages. Seems to be > related to images. After weeks of uptime, you may find firefox is eating > 300M of virtual mem, despite only having one tab open, and to do > *anything* seems to require a sweep through the entire memory set. So it > thrashes around, and brings everything out of swap, and swaps everything > back in, and does the hokey pokey. I hate firefox (why does it have to > walk over the entire memory contents just to open a dialog? Oh, it's that > stupid slow-as-treacle cross platform XUL stuff), and this bug has existed > since day 0, yet no-one bothers about it. I think it also exists in plain > mozilla. Yep, there's an ancient bug opened in bugzilla for it, along > with a whole bunch of tweaks that seem only relevant for windows, and > claims and counterclaims that it is fixed. XUL is actually rather ok. Cross-platformness has its price. And it allows for all the extensions to be created easily. After reading a write-up on gnome.org about lowering GNOME's memory usage in 2.12, I think the problem with Firefox is a bit deeper. The problem is, it allocates more heap memory when required. Then, it free()s some of it. Problem is, when it is in the middle of the heap, i.e. more memory is allocated beyond this free space, it cannot be returned to the OS easily. See http://live.gnome.org/MemoryReduction . Hence, I wouldn't be so rush about calling it Firefoxes bug. What I do is having the session-saver extension installed and when I see that Firefox takes up too much memory, I just quit it and start it again. Voila, back in the same state with a lower memory use. j. -- ______________________________________________________________________________ "We did a risk management review. We concluded that there was no risk of any management." -- Dilbert :wq
Attachment:
signature.asc
Description: Digital signature