mustash: ServerWindows not destroyed when closing app list |
|||
Issue descriptionWhen the app list is opened a hierarchy of 5 ServerWindows is created. When the app list is closed only the top four ServerWindows are destroyed. The ServerWindow at the deepest part of the hierarchy is not destroyed and gets reused next time the app list is opened. The ServerWindow that isn't destroyed has a CompositorFrameSink associated with it. There will be some GPU resources associated with the CompositorFrameSink aren't going to be freed as a result.
,
Feb 16 2017
I suspect the remaining one is for the WebContents used for StartPageView [1]. [1]: https://cs.chromium.org/chromium/src/ui/app_list/views/start_page_view.cc?rcl=db42b5a4025c3ae2402efe7307fc34aee119487d&l=318
,
Feb 16 2017
Shouldn't it go away when the app list is dismissed? Is there some singleton that's left hanging around? And if so - is it an okay behavior?
,
Feb 16 2017
The WebContents is created with user profile (in StartPageService PKS) [1]. It was kept around so that app list can show up fast. Creating a WebContents from scratch takes ~100ms, which is too slow. [1]: https://cs.chromium.org/chromium/src/chrome/browser/ui/app_list/start_page_service.cc?rcl=db42b5a4025c3ae2402efe7307fc34aee119487d&l=382
,
Feb 16 2017
Thanks Xiyuan! Kyle, can you confirm that you only saw the 'new' ServerWindow created (and left around) on the first launch, but not on the subsequent app list launches? If yes, I think we can close this as 'working as intended'.
,
Feb 16 2017
Yep, only the first launch. Sounds like WAI then.
,
Feb 26 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by mfomitchev@chromium.org
, Feb 16 2017Components: Internals>MUS UI>Shell>Launcher
Labels: mustash-1 Proj-Mustash-Mash
Owner: mfomitchev@chromium.org