After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 72142 - Memory leak (>3GB!) and excessive CPU usage.
Memory leak (>3GB!) and excessive CPU usage.
Status: VERIFIED DUPLICATE of bug 66444
Product: nautilus
Classification: Core
Component: general
1.0.x
Other Solaris
: Normal blocker
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-02-21 15:54 UTC by T.D.Bishop
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description T.D.Bishop 2002-02-21 15:54:13 UTC 
This section of the 'top' output clearly shows the problem:

load averages:  0.67,  0.36,  0.24
82 processes:  79 sleeping, 1 running, 2 on cpu
CPU states: 22.5% idle, 11.8% user, 24.0% kernel, 41.7% iowait,  0.0% swap
Memory: 2048M real, 15M free, 3255M swap in use, 2456M swap free

  PID USERNAME THR PRI NICE  SIZE   RES STATE   TIME    CPU COMMAND
13588 tdb        5  21    0 3156M 1730M cpu0    0:39 33.81% nautilus

This is eating all of the systems memory, and some swap. An obvious show 
stopped, resulting in us removing nautilus.

We're using the ximian-gnome binary packages. Specificailly 1.0.4-
ximian.10. Hope this helps.
Comment 1 Michael Petnuch 2002-02-21 21:10:54 UTC 
We need more information.  If you could please tell specifically on
how you can reproduce the bug.
Comment 2 T.D.Bishop 2002-02-21 21:49:16 UTC 
We haven't done anything specific to trigger this bug, other than 
logging in. I can give you more details of our setup, if that helps. 
And, of course, I'll be happy to answer any questions.

We're running ximian gnome 
(http://www.ximian.com/products/ximian_gnome/) on Solaris 8. We use 
this remotely using Hummingbird Exceed. One of the changes we had to 
make to gnome to make this work was setting "Mit-Shm" to "off" in the 
imlib config. I'm not sure if this would affect to workings of 
nautilus. The systems are largish servers with around 2-4gb of RAM... 
we haven't had as much luck replicating this on lower end desktop 
machines (still Solaris).

Other than that, we simply log in and nautilus spins off eating as 
much memory as it can grab. I appreciate this isn't much to go on, 
and there's a lot of other factors involved. Sorry :/
Comment 3 Michael Petnuch 2002-02-21 22:11:52 UTC 
The only thing I can suggest it to try upgrading to the latest stable
version: 1.0.6 and see if that helps.  It might have been fixed already.
Comment 4 John Fleck 2002-03-11 23:35:06 UTC 

*** This bug has been marked as a duplicate of 66444 ***
Comment 5 Michael Petnuch 2002-03-13 04:34:32 UTC 
Good news for you.  This bug did not pertain to nautilus, it was
actually a bug in Orbit making bad writev calls.  So if you upgrade to
the newest ORBit-0.5.14 I've been told that every thing should be good.

See thread for me info if you are interested:
http://lists.eazel.com/pipermail/nautilus-list/2002-March/007700.html
Comment 6 Michael Petnuch 2002-03-13 04:35:48 UTC 
Good news for you.  This bug did not pertain to nautilus, it was
actually a bug in Orbit making bad writev calls.  So if you upgrade to
the newest ORBit-0.5.14 I've been told that every thing should be good.

See thread for me info if you are interested:
http://lists.eazel.com/pipermail/nautilus-list/2002-March/007700.html