New issue
Advanced search Search tips

Issue 908130 link

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



Sign in to add a comment

Long startup due to ProfileManager::GetProfile

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

see:
  1d9a56a0bc72b4ab - 45 seconds
  9c5d21730c3bcc53 - 36 seconds
  f118190e225e88a4 - 32 seconds
  dc3e07ccc4b379ae - 27 seconds
  b25df4ce52450445 - 35 seconds
profile1.png
26.3 KB View Download
profile2.png
24.8 KB View Download
profile3.png
41.3 KB View Download

Comment 1 by ssid@google.com, Nov 25 

Do we have stack samples for these cases, or this is earlier than sampling profiler initialization? 
The traces show a lot of trace events and not one stalled event. It also looks like lot of other events than GetProfile() are also slow. Maybe the system itself is very slow because of IO or CPU ?
Project Member

Comment 2 by chrome-t...@system.gserviceaccount.com, Nov 26

Labels: Restrict-View-EditIssue

Comment 3 by etienneb@chromium.org, Nov 26 

We do not have stackframes for that thread on startup.
I realized that recently, and I'll look why.

Comment 4 by etienneb@chromium.org, Nov 27

Labels: -Restrict-View-EditIssue -Hotlist-HeapProfilingInField -Hotlist-HeapProfilingInField-Trackable Hotlist-SamplingProfilerInField

Comment 5 by etienneb@chromium.org, Nov 27

Labels: -Performance-Memory Hotlist-Jank

Comment 6 by etienneb@chromium.org, Nov 27

Labels: Performance-Browser
►

Sign in to add a comment