Status: Untriaged Owner: ---- CC: [email protected], [email protected], [email protected] Labels: Type-Bug Pri-1 OS-All Area-Misc Size-Medium
New issue 10588 by [email protected]: WaitForSingleObject with INFINITE timouts causing browser hangs for users http://code.google.com/p/chromium/issues/detail?id=10588 Sundar and Karen are both experiencing serious hangs intermittantly. They can create and destroy tabs, but can't load any content or interact with the page. In Karen's case (hang2.dmp), the browser would never respond. In Sundar's (hang1.dmp), it would sometimes come back in 10 seconds or a minute, other times never. I have dumps of both situations here: //www/~jabdelmalek/chrome/hangs/ This is _really_ serious, as the IO thread is blocked on a WaitForSingleObject with INFINITE timeouts. Wan-Teh, I know we've talked about this before a little, but I really think this code needs to be modified, or the waiting can happen on a different thread. As is it's a very frustrating experience for users, and they end up stopping to use Chrome. -- 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 --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
