Commit a8a50478 authored by Evan Stade's avatar Evan Stade Committed by Commit Bot

Remove explicit initialization of notification_ui_manager().

Bug: 578868
Change-Id: I557cc7c90b9632beae9e7b56ca477515abcd67ab
Reviewed-on: https://chromium-review.googlesource.com/896705Reviewed-by: default avatarSteven Bennetts <stevenjb@chromium.org>
Reviewed-by: default avatarScott Violet <sky@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534107}
parent 4041779d
...@@ -2042,12 +2042,6 @@ int ChromeBrowserMainParts::PreMainMessageLoopRunImpl() { ...@@ -2042,12 +2042,6 @@ int ChromeBrowserMainParts::PreMainMessageLoopRunImpl() {
PreBrowserStart(); PreBrowserStart();
// Instantiate the notification UI manager, as this triggers a perf timer
// used to measure startup time. TODO(stevenjb): Figure out what is actually
// triggering the timer and call that explicitly in the approprate place.
// http://crbug.com/105065.
browser_process_->notification_ui_manager();
if (!parsed_command_line().HasSwitch(switches::kDisableComponentUpdate)) if (!parsed_command_line().HasSwitch(switches::kDisableComponentUpdate))
RegisterComponentsForUpdate(profile_->GetPrefs()); RegisterComponentsForUpdate(profile_->GetPrefs());
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment