Comment 7 for bug 66573

The important aspect of my original report was that not only did it grab 100% CPU, but it appears that the plugin grabbed all keyboard/mouse input. In other cases where something eats 100% CPU, the OS scheduler allows other processes to work anyhow, so if I click on some other app's windows, that app will take focus. In this case, it appears that although the cursor moves, all input is being lost. This is classic behavior of an app that does a full X server grab and doesn't release the grab. My suggestion would be to put limits on the kinds of grabs that plugins are allowed to make. Never trust the plugin to do the right thing, especially a proprietary one from a relatively disinterested vendor.