AsyncInitializationActivity.onCreate is slow (low-end) |
|||
Issue descriptionAsyncInitializationActivity.onCreate() takes ~400ms on average on a 512 low-end device. See for example trace.html from crbug.com/735799#c31, where onCreate() took 476.847 ms. Half of it is because of "onCreate->setContentView()" block, which is tracked in issue 762120. The goal of this issue is to investigate what is responsible for the other half.
,
Nov 16 2017
Sounds like Performance-Loading isn't a preferable label. Let me replace it with Performance-Startup so that this bug can be out from loading triage radar.
,
Jan 9 2018
I investigated this a bit in https://docs.google.com/document/d/1OAd1fYv2ugUaiLOTnBPtebNsfvzKaxA-aQVeasmQ6dA/edit#heading=h.5dvxcuuk0mvd and got the following: Out of 412ms taken by AsyncInitializationActivity.onCreate(): 10ms spent in maybeDispatchLaunchIntent() 7ms spent in DocumentModeAssassin.isMigrationNecessary() 14ms spent in super.onCreate() 18ms spent in createWindowAndroid() block 358ms spent in ChromeBrowserInitializer.handlePreNativeStartup() 10ms spent in ProcessInitializationHandler.initializePreNative() 16ms spent in ChromeBrowserInitializer:preInflationStartup() 250ms spent in ChromeBrowserInitializer:setContentViewAndLoadLibrary() 240ms spent in onCreate->setContentView() 80ms spent in ChromeBrowserInitializer:postInflationStartup() That was on 1GiB device though, and latest runs on 512MiB device show that everything ~2x longer.
,
Jan 9 2018
Anyway, I'm closing this for now. I'll reopen if I get time to investigate this more. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dskiba@chromium.org
, Sep 12 2017