Issue 2664: Consider a lock-less painting strategy for windowless plugins http://code.google.com/p/chromium/issues/detail?id=2664
New issue report by [EMAIL PROTECTED]: Consider a lock-less painting strategy for windowless plugins On my T60 dual core laptop, performance is still pretty bad for windowless plugins while scrolling a page if the plugin is animating. Sample sites: http://www.cnn.com/video/?iref=videoglobal http://www.worldofwarcraft.com/ <-- click past the roadblock ad if any These sites run heavy animation loops, which appear to completely dominate the plugin thread. As a result, the lock used to protect the plugin buffer is almost always held, and the renderer gets stuck waiting on that lock a lot. Instead, I think we should employ the same rendering model used to render webkit. That model involves no locks. Instead, the buffer is copied. Moreover, it only paints when the previous paint is acknowledged. That way, the painting is adaptively rate-limited. I believe this approach will result in much better performance. Issue attributes: Status: Untriaged Owner: [EMAIL PROTECTED] Labels: Type-Bug Pri-2 OS-All Area-BrowserBackend -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
