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 598602 - Nautilus uses a lot of heap memory copying large amounts of data
Nautilus uses a lot of heap memory copying large amounts of data
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-15 18:05 UTC by Rex de Jong
Modified: 2021-06-18 15:14 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Pic showing heap memory usage (239.87 KB, image/png)
2009-10-15 18:05 UTC, Rex de Jong 		Details
First valgrind dump attempt (441.31 KB, text/plain)
2009-10-15 18:53 UTC, Rex de Jong 		Details

Description Rex de Jong 2009-10-15 18:05:51 UTC 
Created attachment 145539 [details]
Pic showing heap memory usage

While copying a lot of data (>250GB), Nautilus uses up a lot of memory. This
memory is not given back to the system at any time. Depending on the amount of
copying Nautilus uses from 800MB up to 3GB.

Now using Ubuntu alpha 6 with Gnome 2.28, but this problemed also showed on my
old install (Arch Linux Gnome 2.26)

I attached a printscreen of the memory in the .png. Memory in use that time:
2.4GB. Amount of data copied (not cutted) was about 750GB.

ProblemType: Bug
Architecture: amd64
Date: Sat Sep 26 19:20:11 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.0-0ubuntu2
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-11-generic x86_64

System has 6GB of memory
Comment 1 Cosimo Cecchi 2009-10-15 18:10:17 UTC 
Whoa, perhaps you can attach a valgrind log?
See http://live.gnome.org/Valgrind for more information.
Comment 2 Rex de Jong 2009-10-15 18:40:11 UTC 
If I issue the command mentioned at http://live.gnome.org/Valgrind:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 nautilus &> dump

It stops running after Nautilus is running and makes the dump file. This file is not being changed while copying nor when I close the Nautilus app.

Am I doing something wrong here, or I am I misunderstanding the way it should work?
Comment 3 Rex de Jong 2009-10-15 18:53:49 UTC 
Created attachment 145543 [details]
First valgrind dump attempt
Comment 4 André Klapper 2021-06-18 15:14:03 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.