Posted Nov 1, 2007 15:43 UTC (Thu) by johnkarp (subscriber, #39285)
[Link]
Unfortunately, konqueror uses threads, at least in 3.5. When the kpdf
embedded viewer crashes, as it does, you lose the entire browser as well.
Firefox Extension Issues
Posted Nov 1, 2007 17:43 UTC (Thu) by yokem_55 (subscriber, #10498)
[Link]
I believe you are confusing netscape plugins and kpart components that get loaded. In the case
of kpdf, yes, the kpdf part operates as an in process component, but in the case of an
netscape plugin, they get loaded and run in the nspluginview process and get displayed via
dcop into the browser window.
Firefox Extension Issues
Posted Nov 9, 2007 19:58 UTC (Fri) by Sutoka (guest, #43890)
[Link]
yokem_55 is correct, netscape plugins are ran via nspluginviewer (which
allowed a neat trick of using the 32bit version on a 64bit system to
easily run 32bit plugins in a 64bit browser).
Unfortunately, it's still possible (or was in the past) for Flash to
misbehave very badly and freeze the Konqueror process or even crash it
(I'm not sure I've seen it crash because of Flash since around when Flash9
was released, I'm not sure if thats thanks to Konqueror being improved or
Flash or both though). In the case where Flash (or any other plugin)
freezes Konqueror, I've always been able to unfreeze Konqueror by simply
killing the nspluginviewer process.
IIRC, Konqueror was designed that way to prevent the plugin's main loop
from conflicting with Konqueror's and causing all sorts of nasty
situations.