Version: 3.5.6 (using KDE 3.5.6, Gentoo) Compiler: Target: x86_64-pc-linux-gnu OS: Linux (x86_64) release 2.6.20-rc5 yeah, there have been quite some troubles with (I suppose, badly composed ;) 3rd party plugins. Me too. Under certain circumstances, the plugin runs away with your processor. While not displaying the plugin content. That's not nice, but easy to fix: kill nspluginviewer, reload site. But: average user cannot do this. So plugins won't work until next reboot for them. Now THAT sucks. How to resolve? Maybe some runaway detection (like in the kicker 'runaway progress catcher' or the javascript thingie) including a self destruction mechanism would help alot. So nspluginviewer would kill itself, and reloading the page would start it again. Huh? sincere regards ;)
Hello: It has being a long time since you opened this bug. I've been reviewing the bugs, possibly related and I have some comments. There may be 2 bugs involved in your request: · https://bugs.kde.org/show_bug.cgi?id=206604 which is about (auto)killing nsplugin once is not used · https://bugs.kde.org/show_bug.cgi?id=182869 which is about nsplugin is not performing well. Could you please clarify what do you mean? Thanks.
Dear user, KHTML (and KJS and all related Java/plugin infrastructure) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann