Startup.BrowserWindowDisplay has a lot of samples in overflow bucket. Was trying to look at this metric to analyze some fine grained startup perf changes I did and noticed this. Example: https://uma.googleplex.com/p/chrome/histograms/?endDate=20170130&dayCount=7&histograms=Startup.BrowserWindowDisplay&fixupData=true&showMax=true&filters=channel%2Ceq%2C2%2Csimple_version%2Ceq%2C57.0.2987.8%2Cplatform%2Ceq%2CW%2Cbitness%2Ceq%2C64%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial Should probably increase its range and give it a "2" suffix.
This looks like case where something prevented the browser window from being shown. Background mode and non-browser UI displayed are covered by ShouldLogStartupHistogram(). Are there other factors that prevent a browser window from being shown?
This might be relevant: https://codereview.chromium.org/2798143004/diff/280001/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc#newcode524 (related to apps)
Any movement here?
This looks mostly fixed, for example https://uma.googleplex.com/p/chrome/histograms/?endDate=latest&dayCount=7&histograms=Startup.BrowserWindowDisplay&fixupData=true&showMax=true&filters=platform%2Ceq%2CW%2Cbitness%2Ceq%2C64%2Cisofficial%2Ceq%2CTrue&implicitFilters=isofficial Mark as Fixed?
I think https://codereview.chromium.org/2798143004/diff/280001/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc#newcode524 might have fixed it.
Comment 1 by fdoray@chromium.org
, Jun 16 2017