Bug Description

Doing a search in the shell might lead to unresponsive processes that are not terminated when the search is cancelled or when the gnome-shell overlay is closed.

[ Test case for GNOME-Shell and Nautilus ]

1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one)
2. Open gnome shell overlay (hit super, or got to activity)
3. Search for a short string (3 chars let's say) that matches many files you know you have
4. Close the overlay (press super again, hit escape twice)
5. The nautilus process should stop using CPU once the overlay is closed

[ Test case for GNOME-Shell and GNOME-Calculator ]

1. Run ubuntu session with gnome-shell, and open a system monitor (htop, top, gnome one)
2. Open gnome shell overlay (hit super, or got to activity)
3. Type "10!!!"
4. Close the overlay (press super again, hit escape twice)
5. The gnome-calculator process should stop using CPU once the overlay is closed

[ Regression Potential ]

Nautilus search results returned are missing elements when continuously update the search string, gnome-calculator computations via the shell might not work as expected.

----

I have a maildir for my mail. My computer's name is "nightingale", and this name is in the filenames in the maildir. I have a lot of email!

When I search for "tilix" to start a terminal after logging in, Nautilus goes crazy consuming CPU. This is because I have to type "ti" to type "tilix" and "ti" is a substring of "nightingale". This is submitted as a search string to the nautilus search provider and apparently isn't cancelled when I close the entry - I checked the GError and it's NULL.

A similar thing happens with the ctrl-f search in nautilus itself.

We talked about this on IRC and I provided some traces and stuff. Linking to the log to avoid having to fetch those out into files. :-)