nautilus uses 100% cpu after closing a ssh session

Thanks for your bug. I've forwarded it upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=325979

FYI this still happens in dapper up to date

Yes I can confirm this in both Dapper and Edgy. Whenever the network connection between the two hosts is terminated, nautilus on the client (the one downloading) hits 100% CPU and remains there. It's quite a serious bug because the only way to bring back down the cpu is to do a 'killall nautilus'.

confirmed by saad

i had a similar error when transfering ftp. fix was commited by irc #nautilus user alex to cvs yesterday or the day before.

The upstream bugtracker still shows this bug opened, so maybe the ftp bug is a different one?

I might add that similar behaviour comes up when trying to connect to a remote ssh server fails.

1) add a remote ssh server via "places"
2) doubleclick the shortcut to this server via the desktop.
3) Above does not react now and then (another bug, I know)
4) Nautilus starts using 100% cpu.

Regards

/Martin

Martin, could you get a backtrace (https://wiki.ubuntu.com/Backtrace) when nautilus use 100% cpu?

I also experience this bug regularly when copying (large) files from a NFS-mounted directory.
Nautilus consumes > 80% of CPU-usage after the copy-process is finished.

I've been living with this bug for quite a while now; and I thought it would be fixed pretty soon since the bug is listed here and Nautilus is a major component of the GNOME-Desktop.
Hope it will be fixed soon and updated via new packages.

I can also confirm this problem in Feisty on amd64. Hope it gets fixed sometime.

I'll add another "me too" to the list.

Me to, when I shut-down the computer while ssh-ing with it nautilus gets sick but after a while (about 10 min) nautilus is being healed and does not consume more cpu than normal...

I am still experiencing this in Feisty.

What seems to regularly reproduce the problem for me is to delete a file on the ssh server (from Nautilus). Shortly after Nautilus goes to 100% CPU. I would guess that the bug stems from Nautilus assuming that the deleted files are still there and doing an operation based on that incorrect assumption, resulting in a spin-lock.

I just experienced this in Gutsy, so it hasn't been fixed yet...

On my Gutsyfied (from Feisty to Gutsy beta) Thinkpad T23 Nautilus goes to 100% CPU when the Gnome session is terminated. Best way to see this is to switch user from A to B, terminate user B's session and go back to A. The CPU is pegged with user B's dying Nautilus.

Possibly related: I quite often have to shoot down bonobo-activation-server to get Nautilus to start after having logged in and out once without a reboot.

Terminating Nautilus (using nautilus -q) also leads to the dying nautilus hogging the CPU, all the while spewing dire '0x8177880 2007/09/30 23:26:54.2265 (USER): debug log dumped due to signal 11' warnings into nautilus-debug-log.txt at a rate of app. 7000 messages per second. After killing the morbid nautilus the CPU gets pegged by tracker which insists on indexing this logfile (easily remedied by deleting the offending log file but still...)

nth-ing here on Gutsy beta.

My reproduction:
1. Start nautilus on machine A
2. On machine A, have nautilus connect server (ssh) to machine B
3. Copy files from machine B to machine A
4. Turn off machine B
5. Machine A's nautilus is now stuck at 100%

What commands can I run to give more useful info?

Hi
I got the same trouble with Gutsy, but I figured out that, when I "Close" or Umount the SSH connections, Nautilus comes down to normal.
It looks like Nautilus tries to keep the SSH connections alive spending 100% of CPU power. Sad thing is, that I now always need to Reconfigure the connection to the SSH server.

cheers Claus

I get the same as screwITfix on gutsy. It takes about 10 seconds for nautilus to come down from 100% CPU usage when you unmount the connection

Ok, so this bug is about two years old now.. I guess it's related to my problem: In Edubuntu the clients connect via SSH. After people log out a Nautilus process is sometimes left running @ 100% CPU forcing me to kill it. It happens almost every day and slows the server (and clients) to a crawl.

What can I do to help get this fixed?

I can also confirm this bug, using Nautilus 2.20.

I am also confirming this bug, connecting to my desktop from my laptop via Places -> Connect to Server in the Gnome menu and selecting ssh and providing the server ip (in this case 192.168.0.104 note using private key authentication). Nautilus' CPU utilization will spike to 100%.

If I right click on the folder created to the desktop that says "sftp on 192.168.0.104" and choose unmount volume, the CPU usage returns to normal.

Here's some info that may be helpful:
ryan@lappy:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid

ryan@lappy:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.24.1-0ubuntu1
  Candidate: 1:2.24.1-0ubuntu1
  Version table:
 *** 1:2.24.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

I am having difficulty reproducing the bug, I never actually noticed when it spiked, but I was checking top and noticed that nautilus was using 100% CPU. It remained like this for several minutes until I took the steps mentioned in the previous post (unmounted the sftp folder)

Doing that immediately reduced the CPU usage to a much lower %.

I have similar problem but with samba-mounts. Unfortunately I can not reproduce, but I had two samba mounts via nautilus, one of them caused nautilus to use 100% CPU, as unmounting reduced the cpu-usage immediately.

We use SFTP for managing multiple websites. This is a total pain and is making Ubuntu unusable in our core business. The bug seems to have been in Ubuntu since January 2006 - surely there must be a fix for this critical bug by now??? Nautilus is still consuming 100% of CPU even after a cold re-boot.

the bug is not happening to everybody and there is no clear way to trigger it

Solved it we hope! Dump Nautilus; use Konqueror.

I think that this is not right way to handle a bug that has been reported since three years and through even more distros releases.

I've just landed here for the first time since I'm using nautilus for sftp and was worried by this strange cpu activity even - and especially - after the download would end, fearing that my transfers could not have been cleanly closed. True that ie used in the past (more than a year ago) sftp and didn't recall this behaviour.

I can reproduce at any tine: just open a remote sftp window and transfer (I've dragged the directory from my local directory window and dropped). Can see any other special setup that could influence, except that I 'm running a SSVNC session thus having two ssh sessions. Also I'm using key authentication, in case this matters.

Just another hint that just happened: I've tried to unmount the sftp folder and the desktop was frozen (only, other app widows would work normally) then all icons simply disappeared. Killing the sftp process made reappear the desktop icons.

So maybe it a problem rather linked to the display of the sftp volume on the desktop. In the past I had complain to no avail to the rather lousy implementation of this desktop icon, which bring you back to root directory after first login, so maybe it's more a dbus issue or whatever.

Marking this task for Mandriva as Invalid since it's not necessary. Please only open a new task for another project when you're actually reporting a bug there or when it's the proper upstream of the package.

Moving this to GVFS since comments in the upstream GNOME bug report indicate that this issue is/was GVFS related; gedit is also affected.
Can anyone actually still confirm this bug after all those years?

I can confirm this bug, even after all this time. It drives me absolutely bonkers and causes all sorts of problems for me. I moved the SSH off of Nautilus and it got a bit better, but I observe the exact same behavior when I'm connecting to FTP servers with Nautilus' ftp:// transport. It makes even navigating local files nearly impossible.

I can confirm this bug. Running Ubuntu 8.04.4 (Hardy) on Toshiba Satellite A15-S129 and HP Pavilion a400n. Regularly use File Manager (Nautilus) via SSH between the two. After some period of inactivity, return to find both machines at around 60% CPU.

Please fix this bug: http://oi49.tinypic.com/soo1nk.jpg

Upstream says the issue is fixed in the current version