Issue 3613: HANG [winqual] WebContents::Destroy http://code.google.com/p/chromium/issues/detail?id=3613
Comment #3 by [EMAIL PROTECTED]: I chatted with several people about this bug. It seems likely that the cause is a plugin is hung. EnumChildWindows is trying to communicate with that hung window, although we don't specifically know which synchronous message it might be sending. The hung plugin monitor should have come up in this case. The dialog could have been behind the main window and the user didn't notice, or they could have killed the app in the period of time after Windows thinks the app is hung (something like 10s) but before we think the plugin is hung (I think 30s). I don't think there's a lot more we can do here other than making the hung plugin dialog in sync with the timeout for Windows' one (which we tried and it didn't work out too well). I filed bug 3691 for an idea we had to make this better specifically when exiting, although we would still have the window of time where Windows thinks we're hung. In short, this should not block 1.0. -- 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 chromium-bugs@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
