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 -~----------~----~----~----~------~----~------~--~---
