Ubuntu
nautilus package

Nautilus uses lots of memory when deleting directory with many small files

Bug #105286 reported by Mika Fischer on 2007-04-10

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	Expired	Medium	gnome-bugs #439766
	nautilus (Ubuntu)	Invalid	Low	Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I have a directory containing about 60000 small BMP images (2 kB each). When I open it in Nautilus and wait until it has generated its thumbnails and then go to the parent folder and try to delete the directory (I'm using SHIFT+Delete), Nautilus starts eating memory until I kill it. Attached is a screenshot where Nautilus has a VSS of about 3 GB! Smells like a memory leak somewhere...

I'm running a current Feisty installation.

Revision history for this message

Mika Fischer (zoop) wrote on 2007-04-10:

Screenshot showing Natilus' excessive memory usage Edit (57.3 KiB, image/png)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-04-13:

Thank you for your bug. Looks like an upstream bug

Changed in nautilus:
assignee:	nobody → desktop-bugs
importance:	Undecided → Low
status:	Unconfirmed → Confirmed

Revision history for this message

Mika Fischer (zoop) wrote on 2007-05-19:

So did you file a bug in the Gnome bugzilla? Or am I supposed to do that?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-05-19:

No, I didn't, somebody getting the bug and who can reply to upstream question should open it

Mika Fischer (zoop) on 2007-05-19

Changed in nautilus:
status:	Unconfirmed → Unknown

Bug Watch Updater (bug-watch-updater) on 2007-05-20

Changed in nautilus:
status:	Unknown → Unconfirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-05-20:

Thank you for sending it upstream

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-06-25:

could you try if that's still an issue in hardy?

Changed in nautilus:
status:	Confirmed → Incomplete

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-07-14:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to 'New'. Thanks again!