New issue
Advanced search Search tips

Issue 825250 link

Starred by 2 users
Status: WontFix
Owner:
mheikal@chromium.org
Closed: Jul 11
Cc:
agrieve@chromium.org
mheikal@chromium.org
yfried...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug

Blocking:
issue 819794



Sign in to add a comment

Investigate what happens in Looper.dispatchMessage after navigationStart

Project Member Reported by dskiba@chromium.org, Mar 23 2018 
Attached is an excerpt from MapsGo startup trace on 512MiB Android Go device (gobo_512 @ OMB1.180212.001).

As you can see we spent 600ms in Looper.dispatchMessage.

First, it seems we're missing TraceEvents in some top-level function (finishNativeInitialization?).

Second, why exactly we spent so much time there?
no-traceevents.png
30.6 KB View Download

Comment 1 by dskiba@chromium.org, Mar 23 2018

Blocking: 819794

Comment 2 by mheikal@chromium.org, Mar 26 2018

Owner: mheikal@chromium.org

Comment 3 by mheikal@chromium.org, Apr 4 2018 

This takes only 214ms on my Android Go 1GB phone, I have attached a screenshot of trace as well as the trace itself that is more annotated with trace events. I am not sure if something looks suspicious?
Screenshot from 2018-04-04 13-06-57.png
41.2 KB View Download
output.html
9.7 MB View Download

Comment 4 by yfried...@chromium.org, Apr 5 2018 

ToolbarManager.initializeNative (presumably?) looks to be nearly 30ms of that. Is that the same issue Dmitry was looking into of not inflating toolbar too early?

Comment 5 by yfried...@chromium.org, Jul 11

Status: WontFix (was: Available)
not reproducible now and also irrelevant now that we start navigation much earlier
►

Sign in to add a comment