I just pinged Avi about us, my guess is that the Sandbox is blocking connections ot the Window Server. Adding (debug deny) to the sandbox spec file will print messages to console when things like this happen, I'll add a note about that to the Wiki ( http://dev.chromium.org/developers/debugging-on-os-x).
Best regards, Jeremy On Fri, May 22, 2009 at 10:54 AM, Avi Drissman <[email protected]> wrote: > A visitor to IRC pointed me today to http://crbug.com/11319 , where > renderers are marked as "not responding". He pointed out that this is not > just a cosmetic issue, since things like spindump run which kills > performance on non-quad core machines (that we all have). > > I thought about just pumping events on a non-main thread, but it turns out > that NSApp nextEventMatchingMask returns nil when you don't run it on the > main thread and doesn't pull any windowserver events. > > I thought about going for LSBackgroundOnly, but 1) we don't have a separate > bundle for the renderer and 2) I don't know if that fixes our problem. > > The only thing I can think of now is to create the MessageLoopForIO in > renderer_main in a non-main thread and make a MessageLoopForUI on the main > thread. > > Any thoughts on how to better do this? > > Avi > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
