Nautilus using high amounts of ram

[Tray Salter]

My System (Amd64 x2 dual core 2.6 Ghz, 4GB ram, nvidia 9400 gt with 1gb vid ram) is using 463.8 MiB ram for Nautilus. this started happening after upgrading to 9.04 (jaunty). My system , on the average before the upgrade, used a total of 700 - 800 MiB ram for day to day use. Now I am at over 1.3 Gb ram just idling.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Tray Salter (traysalter)]

here is the valgrind log. I have restarted my system so the ram usage at this point is down to 20 Mib. if you like i can re-run this when the ram had gotten higher again.

[Tray Salter (traysalter)]

I opned a folder with a log of jpgs. them ram used by nautilus jumped from the 20.1 Mib to 312.8. I have closed the folder but Nautilus has not released the ram. I re-ran the valgrind and have uploaded the new file for review as well.

[Sebastien Bacher (seb128)]

there is no issue listed in those logs, did you stop the running instance before starting one under valgrind? do you have videos or other thumbnailed files in the directories you browse?

[Tray Salter (traysalter)]

I had rebooted the entire system before the first log. I did not reboot or restart Nautilus before doing the second log. when I open a directory with jpgs the mem usage goes way up. Nautilus never releases the memory once the folder is closed again. the memory stays in use my Nautilus until I reboot the system, even if all Nautilus windows are closed.

[Tray Salter (traysalter)]

Here is a screen capture of the system monitor after a reboot, then as I open a folder with a ton of jpgs. then I close it..re - open and close it again. Open a different folder. then clos them all. and the memory doesnt drop.

[Sebastien Bacher (seb128)]

you can close nautilus using "nautilus --quit" and then run it under valgrind

[Tray Salter (traysalter)]

here is the log generated by doing that last option. The memory usage got up to 684Mib that time

[Sebastien Bacher (seb128)]

there is no obvious error there, could you add "--leak-check=full --show-reachable=yes" to the valgrind options and try stopping nautilus using nautilus --quit?

[Sebastien Bacher (seb128)]

having a testcase or an example of file leading to the bug would be useful there

[Tray Salter (traysalter)]

options added. I quit Nautilus and then ran the command for valgrind. this is the output log. I hit almost 740 MiB of ram usage. I opened the main folders that increase the ram usage. My Issue is that Nautilus isnt releasing the ram once windows are closed.

[Sebastien Bacher (seb128)]

there is nothing obvious there still, it shows libxml use, perhaps upstream would have a better clue about the issue

[Pedro Villavicencio (pedro)]

Hello Tray, Is this still an issue for you? Could you try in Karmic? any news on the upstream bug ? did you sent it there? may you tell us the bug number ? Thanks.

[Tray Salter (traysalter)]

I have changed from the 64 bit to the 32 bit jaunty and no longer seem
to be having the issue.

Pedro Villavicencio wrote:
> Hello Tray, Is this still an issue for you? Could you try in Karmic? any
> news on the upstream bug ? did you sent it there? may you tell us the
> bug number ? Thanks.
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Incomplete
>
>

[Pedro Villavicencio (pedro)]

Ok thanks you for the quick response Tray, I'm closing this for now then , since we don't have any duplicates and no other users indicating the same issue, please re open or file a new bug if you face the issue again, thanks in advance.