[Bug 155543] Plasma stops responding after some operations

[Roman Standzikowski]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=155543         




------- Additional Comments From romanujan gmail com  2008-01-13 13:23 -------
> yes, shocking: bad code can disrupt an application! horror! 

Maybe... But more and more applications tries to run plugins in separate processes, to avoid crashes. Look here:

http://zrusin.blogspot.com/2007/05/browser-plugins.html
http://amarok.kde.org/blog/archives/76-Inside-amaroK-1.4-Collection-Scanner.html

I'm not sure, but if I remember correctly the Firefox guys consider doing the same, so that a bug in Adobe Flash Player or Acrobat Reader won't crash the whole browser (I cannot find this info right now). 
The more easy writing plasmoids is, the more unskilled developers will code their own widgets, and since Plasma desktop is a very important application...

I hope you will at least consider similar solution. A pitty I cannot convert this bug report into a wish - it seems more appropriate now.

> as for threaded painting, there's a set of patches floating around for that. 
> they didn't make it for 4.0 and i hope the author has time to come back to
> them for 4.1. 

That would be great, this would probably solve the issue :D And since 32-core CPUs will eventually find a way to our desktops...

I guess from my point of view this is the end-of-topic. I have reported the problem, you don't need my help with reproducing it, I have explained my point of view - so THE END :)