A. Walton, as requested, I ran nautilus under valgrind using the massif heap profiler. I ran this command line after executing "nautilus -q":
$ valgrind --tool=massif nautilus This was the output on the shell: ==18680== Massif, a heap profiler. ==18680== Copyright (C) 2003-2007, and GNU GPL'd, by Nicholas Nethercote ==18680== Using LibVEX rev 1804, a library for dynamic binary translation. ==18680== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==18680== Using valgrind-3.3.0-Debian, a dynamic binary instrumentation framework. ==18680== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==18680== For more details, rerun with: -v ==18680== seahorse nautilus module initialized Initializing nautilus-share extension ** (nautilus:18680): WARNING **: Unable to add monitor: Não suportado GLib-ERROR **: /build/buildd/glib2.0-2.16.3/glib/gmem.c:175: failed to allocate 1073741824 bytes aborting... ==18680== Finalizado The last word means "Finished", meaning (maybe i don't know) that the process was killed (not by me). My PC almost locked down because this time nautilus eat up all my RAM and little over 50% of swap. The valgrind file output is attached. By the way, I have a 701MB .avi file on my home folder. My current PC configuration: Intel(R) Pentium(R) 4 CPU 2.40GHz 1232MB RAM 40GB IDE Disk When I get home, I'll run valgrind with another PC configuration ** Attachment added: "Nautilus Valgrind Massif Output" http://launchpadlibrarian.net/14477256/massif.out.18680 -- nautilus memory leak https://bugs.launchpad.net/bugs/204413 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
