Comment #10 on issue 3613 by bugdro...@chromium.org: HANG [winqual]
WebContents::Destroy
http://code.google.com/p/chromium/issues/detail?id=3613
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=9756
------------------------------------------------------------------------
r9756 | jos...@google.com | 2009-02-13 08:59:22 -0800 (Fri, 13 Feb 2009) |
25 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/tab_contents/web_contents_view_win.cc?r1=9756&r2=9755
Check for hung plugin windows before detaching them
The process of detaching plugin windows from tab window
involves windows messages across browser and plugin process.
If the pungin process is hung this hangs the browser
shutdown sequence.
This workaround first checks if the plugin is responsive
before detaching its window from the tab. If a plugin is
hung, it's window would not be detached (and would be
destroyed with the tab window).
The side effect of not detaching is that some plugins
expect their window to be valid until they get NPAPI
shut down notifications and may crash if those
notifications were sent after the window was destroyed.
But since the plugin is hung anyway, we can go ahead
not detaching the window. Plugin process will be
cleaned up later.
BUG=3613
Review URL: http://codereview.chromium.org/20301
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
