Updates:
Summary: WidgetWin destruction needs inspection, reworking
Comment #4 on issue 27347 by [email protected]: WidgetWin destruction
needs inspection, reworking
http://code.google.com/p/chromium/issues/detail?id=27347
I'm tempted to raise this to P1. Here's why:
If code has a scoped_ptr to a Widget, and calls Close(), then resets the
pointer, the
hwnd backing the widget is hidden, but never actually destroyed, because
CloseNow()
is produced by a scoped runnable method factory that is destroyed and thus
cancels
the call. The hwnd will live on, zombie-like, until its parent hwnd is
destroyed.
There are two mitigating factors:
* I'm not sure how common this idiom is.
* We don't have tons of hwnds, so it's unlikely (but I suppose possible)
this is
going to manifest in visible bugs.
--
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
