Hello!

During some time while using GNOME the Nautilus stops to react on requests to open a new window. Starting Nautilus from a shell just returns immediately with return code 0, nothing happens, no output to system-log or dmesg. The same happens if someone clicks on the icon for Nautilus on the dash of GNOME-Shell.

Affected Versions: Nautilus >= 3.10.0
Config: gnome-session-properties launches "nautilus -n", the default
Logs: nothing in dmesg or journalctl -b

Steps to reproduce:
1. Launch a GNOME-Session and work for some hours, with and without Nautilus
2. At some (random) time the background-process of Nautilus (launched by gnome-session-properties) will use 100% of a single CPU-Core
3. Nautilus won't open a window anymore if requested to do so

Steps to recover:
1. $ pgrep nautilus
2. $ kill $PID
3. $ nautilus -n
4. Nautilus-windows can be opened for some time again (~hours)

Output of ps:
$ ps -lfp3760
F S UID        PID  PPID  C PRI  NI ADDR SZ WCHAN  STIME TTY          TIME CMD
0 S peter     3760     1 99  80   0 - 381035 poll_s Dec04 ?       1-01:55:15 /usr/bin/nautilus --no-default-window


Sources:
https://bbs.archlinux.org/viewtopic.php?id=172019
Also with a screenshot, propably a quad-core. Please note that I found some old "100% load" bugs but non current and fitting to this actual issue.


Thank you