On Fri, Jan 28, 2005 at 04:15:24PM -0800, David Schleef wrote: > On Fri, Jan 28, 2005 at 11:32:30PM +0100, Sven Luther wrote: > > Hello David,
Thanks for CCing me on the bug report :) > > I understand you gave the free hand on upping the severity in a previous > > mail, > > so why do you disregard this now ? > > Because the comments since the 0.3.2-2 upload have only mentioned > CPU usage, which is _completely_ uninteresting w.r.t. this bug. > swf_play can scale CPU usage by as much as a factor of 10, using > as much as possible for better quality. This is not a bug. Well, CPU usage would be ok, but i feel that it is using excessive CPU usage, and furthermore i feel that even 4 processes are using *all* the CPU power available, and it seems to be also linked with the available memory. I have had at least 3-4 such reports, and am asking Ingo to also mention his experience with this. All those i know have disabled swf-player to solve the issue. Do you have an idea of why so much cpu power is used ? And maybe some kind of control option, ideally set at install time depending on the number of processors, would help in this case ? > > | Looked closely at top. And there it was. swf_play. Four instances each > > | claiming 25%+ of cpu. Quit Firefox and swf_play remains+as a memory hog. > > If swf_play processes are not being destroyed when the page changes > or when the browser is killed, that's a problem. But I have not seen Well, I think that having the machine crawl to uselessness is also a problem. No other package i run does that on my hardware. > this problem, and there's no mention of it (until now) on this report. Err, i also mentioned having to kill those processes by hand in the original bug report, didn't i ? Well, they where not limited to 5 back then though. BTW, would it be possible to make the number of helper processes a config option that can be changed, so we can better experiment and look after these. > Feel free to provide more information about _that_ problem. Gladly, what kind of information do you need in addition on what we have already ? Basically 4 processes eat all cpu usage (and probably a big chunk of memory too), and stay even when you kill the browser, and have to be killed by hand. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
