Basically, searches never stop by themselves, which result in abnormally high constant CPU usage by nautilus.

The bug is producible with 2 use cases.

1. Files search

1.1 Open "Files"
1.2 Search for something
1.3.A Expected behaviour: when all the results are found, the search should stop.
1.3.B Result: the search never stops (and CPU use remains high) even when all possible results are shown on the current view.

If the user stops the search him/herself, then all returns to normal.

2. Gnome Shell search

1.1 Open the shell view 
1.2 Search for something (e.g. an app to launch)
1.3 The nautilus process is now stuck at high CPU usage.

The user has to terminate the process (e.g. using gnome-system-monitor).