Description Sergey Shelukhin 2017-06-22 17:42:58 EDT

At some point when a background operation (e.g. an auto-build, refresh, etc.) is blocking a user operation (e.g. saving), Eclipse shows a progress dialog with tiny cancel buttons. At that time, the IDE is also often slow due to the aforementioned background operations.
What I (and others, I suspect) do every time this happens is hunt for each of the tiny red squares for the background ops, and click it; or mash it, UI being unresponsive. The reason, other than mere impatience, being that if the operation goes into GC death or  otherwise hangs, a save might not go thru and some edits will be lost. 
It would be nice to have a feature where a user operation would automatically kill any blocking background operations at the time when the dialog would normally appear. They may not die immediately but it's an improvement over hunt-and-mash before the kill. Perhaps it could even be more aggressive than the dialog box.