Comment 108 for bug 2697
Revision history for this message
|
|
#108 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
(In reply to comment #77)
> I'm not sure this bug is the appropriate place to put "Bug 457950". I wasn't
> so concerned with a plugin crashing the browser (though that is a concern), I
> was more concerned that a plugin (Adobe flash) running in one window, wants to
> use all of the CPU.
The issue is different from the user perspective, but the solution is identical: run plugins in their own process. From a development perspective it's the same request.
Yes, you could solve your problem by using only threads, not processes, but that's unlikely to happen precisely because it doesn't solve the security problem, whereas using separate processes *would* help to solve the multicore utilization problem.
> There isn't a CPU crisis -- it's just 1 cpu that's busy. Why can't those
> plugins get a separate thread ?
They can. That's what this bug requests. It will just take a considerable amount of development work.
FYI, this is not being ignored, IE8 and Chrome have gotten Mozilla talking about process-per-tab (and I guess -per-plugin too). See some discussion here, at least on process-per-tab:
http://
But I get the impression that it's going to take a lot of work to implement.