On Thu, 2010-04-15 at 02:08 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 2010-04-14 at 18:38 -0400, Felix Miata wrote:
On 2010/04/15 00:10 (GMT+0200) Carlos E. R. composed:
The problem is that Firefox is a memory hog. PR VIRT RES SHR S %CPU %MEM COMMAND 20 123m 52m 13m R 26 0.7 npviewer.bin 20 867m 232m 31m S 2 2.9 firefox What uptime, and how many tabs? Sometime days, sometimes minutes. These are all 14 days uptime with average tab count 11.75: %CPU %MEM VIRT RES SHR COMMAND TIME+ 3 9.3 697m 373m 12m X 333:33.59 For 12 tabs... I guess that doesn't seem unreasonable. And it depends a great deal on the sites in question. That's ~33MB per tab, generously. Given what a modern browser has to deal with I don't see a terrible issue. The thing is that you close all the tabs but one and it still uses
On 2010-04-15 01:34, Adam Tauno Williams wrote: that much memory.
Yes, and no. The definition of "uses" is important. In UNIX pages typically are not recovered from an application unless there is memory pressure; doing so is just a waste of effort. A long running process will be as large as it is as the largest point - it is a feature, not a bug. Within the process those pages can be recycled.
You have to exit (with save tabs) and start it again: hey, now mine uses about 600 megs instead of 900 as before. A lot of that gigabyte was unused memory holes.
Exactly, and if the systems needs the 'space' occupied by those holes it can throw them out to swap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org