New issue
Advanced search Search tips

Issue 908128 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
etienneb@chromium.org
ssid@chromium.org
gab@chromium.org
devlin@chromium.org
fdoray@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Long startup due to InstalledLoader::LoadAllExtensions

Project Member Reported by etienneb@chromium.org, Nov 23 
We are receiving slow-reports where the startup is quite long due to load all extensions.

See:
  0ce405e2a25f2703 - 45 seconds
  ac20f0b11d2f87cb - 43 seconds
  380100b0ef75112a - 19 seconds
  957e264846b7a947 - 17 seconds
  3ef16cc7d3b5474e - 15 seconds

The task is not stalled since we can observed multiple ScopedBlockingCall.
load_extensions1.png
23.4 KB View Download
load_extensions2.png
18.3 KB View Download
load_extensions3.png
40.6 KB View Download

Comment 1 by etienneb@chromium.org, Nov 23 

Unfortunately, the sampling profiler on the main thread is not started before the runloop is available. Thus, we do not have useful stackframes on these traces yet.

Comment 2 by etienneb@chromium.org, Nov 23

Cc: etienneb@chromium.org

Comment 3 by ssid@google.com, Nov 25 

Re #2: We can start sampling profiler when tracing starts and later register a trace log observer by calling TracingSamplerProfiler::OnMessageLoopStarted(). Would it work if we called TracingSamplerProfiler::CreateOnMainThread() in ChromeMainDelegate constructor?

Comment 4 by etienneb@chromium.org, Nov 26 

The sampling profiler is not running on startup.
That needs to be fix. We will update this bug after.
►

Sign in to add a comment