Your message dated Wed, 13 Sep 2006 01:57:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386149: firefox: virtual size in "top" increases to over 
200MiB, becomes sluggish after significant use
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: firefox
Version: 1.5.dfsg+1.5.0.6-3
Severity: normal


After opening several tabs and loading several web pages, Firefox's 
virtual size as shown in "top" increases to 250 MiB or so, and doesn't 
decrease until it is restarted. Firefox becomes sluggish, particularly 
with actions like "save link as".

Are there any user configurations that could help alleviate this 
problem?

Regards,

Arthur.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages firefox depends on:
ii  debianutils               2.17           Miscellaneous utilities specific t
ii  fontconfig                2.3.2-7        generic font configuration library
ii  libatk1.0-0               1.12.1-1       The ATK accessibility toolkit
ii  libc6                     2.3.6.ds1-4    GNU C Library: Shared libraries
ii  libcairo2                 1.2.4-1        The Cairo 2D vector graphics libra
ii  libfontconfig1            2.3.2-7        generic font configuration library
ii  libfreetype6              2.2.1-2        FreeType 2 font engine, shared lib
ii  libgcc1                   1:4.1.1-13     GCC support library
ii  libglib2.0-0              2.10.3-3       The GLib library of C routines
ii  libgtk2.0-0               2.8.20-1       The GTK+ graphical user interface 
ii  libjpeg62                 6b-13          The Independent JPEG Group's JPEG 
ii  libpango1.0-0             1.12.3-2       Layout and rendering of internatio
ii  libpng12-0                1.2.8rel-5.2   PNG library - runtime
ii  libstdc++6                4.1.1-13       The GNU Standard C++ Library v3
ii  libx11-6                  2:1.0.0-8      X11 client-side library
ii  libxft2                   2.1.8.2-8      FreeType-based font drawing librar
ii  libxinerama1              1:1.0.1-4.1    X11 Xinerama extension library
ii  libxp6                    1:1.0.0.xsf1-1 X Printing Extension (Xprint) clie
ii  libxt6                    1:1.0.2-2      X11 toolkit intrinsics library
ii  psmisc                    22.3-1         Utilities that use the proc filesy
ii  zlib1g                    1:1.2.3-13     compression library - runtime

firefox recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
* Arthur Marsh ([EMAIL PROTECTED]) wrote:
> 
> 
> Eric Dorland wrote:
> >* Arthur Marsh ([EMAIL PROTECTED]) wrote:
> >>Package: firefox
> >>Version: 1.5.dfsg+1.5.0.6-3
> >>Severity: normal
> >>
> >>
> >>After opening several tabs and loading several web pages, Firefox's 
> >>virtual size as shown in "top" increases to 250 MiB or so, and doesn't 
> >>decrease until it is restarted. Firefox becomes sluggish, particularly 
> >>with actions like "save link as".
> >
> >It won't ever decrease, once memory is allocated to a process it is
> >never reclaimed. It should stabilize though, does it? 
> 
> It does appear to stabilise, but it can get to the stage where Firefox 
> is too slow to be considered responsive (I have 256 MiB of RAM on this 
> machine and can only upgrade it as far as 384 MiB with considerable 
> expense).

Programs take memory. It's entirely possible with your setup 256MiB
isn't enough for good performance. 
 
> >
> >I have no idea why the save link as is slow, but that may have more to
> >do with GTK then firefox.
> 
> I do suspect there are some issues with GTK having to examine every file 
> in the directory being saved to. If one is doing a save, I only expect 
> to be informed of:
> 
> 1) directories within the directory being saved to; and
> 
> 2) any file with the same name as the file being saved to (and if that 
> happens, I don't mind if GTK examines the existing file causing the 
> collision).
> 
> What was annoying was having the "save as" dialogue box still present 
> several seconds after pressing the "save" button when using a directory 
> on a local vfat file system with about 500 files in it.

Feel free to file a bug against GTK. 

> > 
> >>Are there any user configurations that could help alleviate this 
> >>problem?
> >
> >Certainly using as few extensions and plugins as possible would help. 
> >
> 
> OK, will try trimming them back. I'm not sure how to disable the 
> Blackdown Java plug-in though. Firefox seems to pick it up from the 
> ~/.mozilla/plugins directory.

I'm not really seeing a specific bug here, and we already have bugs
open about firefox taking too much memory, so I'm going to close. Feel
free to reopen if you disagree.

-- 
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]
1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to