On Mon, Apr 13, 2009 at 12:13 PM, Darin Fisher <[email protected]> wrote: > The Mac implementation is wrong. On a single core machine, the renderer > could starve the UI thread of the browser, preventing any pixels from ever > being updated on the screen.
That seems wrong--the OS-prompted draw should be just blitting from the backing store, right? But I'm more concerned about this starvation problem--the renderer should not be able to starve the UI thread under any circumstances--we always need to return to the main runloop every second or two or the OS will decide we're unresponsive and beachball. What code path can cause this? --Amanda --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
