New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 821604 link

Starred by 1 user
Status: Fixed
Owner:
█ dschuyler@chromium.org
Last visit > 30 days ago
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

106ms startup performance regression in OmniboxResultView::OmniboxResultView()

Project Member Reported by wittman@chromium.org, Mar 13 2018 
Data from the UMA Sampling Profiler shows that OmniboxResultView::OmniboxResultView() regressed browser process UI thread startup on 64-bit Chrome on Windows by 106ms. This occurred in the 67.0.3367.0 Canary release.

The responsible CL appears to be https://chromium.googlesource.com/chromium/src.git/+/8ec2a06321af1ec8b42cecd1df8f29d254b5b52b

Execution profile difference of Canary 67.0.3366.0 vs. 67.0.3367.0: https://uma.googleplex.com/p/chrome/callstacks?sid=c9e6f7c66af552df713deb61fd2d27c9

Comment 1 by wittman@chromium.org, Mar 20 2018

Status: Fixed (was: Assigned)
This regression was resolved with the partial revert of the original change in 67.0.3371.0: https://chromium.googlesource.com/chromium/src/+/533531b66bad97c1784290a012fd7b411cd60057.

Execution profile difference of Canary 67.0.3370.0 vs. 67.0.3371.0: https://uma.googleplex.com/p/chrome/callstacks?sid=c598a72a74c651bba08a21bbb2116d89
►

Sign in to add a comment