Chrome Home sheet opens laggily |
|||||
Issue descriptionChrome Version: 63.0.3226.0 OS: Android / Pixel What steps will reproduce the problem? (1) Open Chrome with Chrome Home enabled (2) Swipe up panel What is the expected result? Panel opens smoothly What happens instead? It opens with a lag (seemingly stuck for several 100ms) - see video Note: This does not repro on Chrome Dev. about://chrome ---- Google Chrome 63.0.3226.0 (Official Build) canary (32-bit) Revision 209b73b2d53c279870bd421b7c04a1427798e2ef-refs/heads/master@{#504841} OS Android 8.0.0; Pixel Build/OPR1.170623.027 Google Play services SDK=11029000; Installed=11836940; Access=1p JavaScript V8 6.3.220 User Agent Mozilla/5.0 (Linux; Android 8.0.0; Pixel Build/OPR1.170623.027) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3226.0 Mobile Safari/537.36 Command Line --use-mobile-user-agent --top-controls-show-threshold=0.5 --top-controls-hide-threshold=0.5 --use-mobile-user-agent --enable-pinch --enable-viewport --validate-input-event-stream --enable-longpress-drag-selection --touch-selection-strategy=direction --disable-gpu-process-crash-limit --main-frame-resizes-are-orientation-changes --disable-composited-antialiasing --ui-prioritize-in-gpu-process --enable-dom-distiller --flag-switches-begin --enable-features=ChromeHome --flag-switches-end --top-controls-show-threshold=0.5 --top-controls-hide-threshold=0.5 --top-controls-show-threshold=0.5 --top-controls-hide-threshold=0.5 Executable Path No such file or directory Profile Path /data/user/0/com.chrome.canary/app_chrome/Default Variations c641c173-3f4a17df 6a89113b-f23d1dea 853359fa-f23d1dea 16e0dd70-3f4a17df 61fba06-ca7d8d80 da89714-4ad60575 241fff6c-ec1be22a 1e528f0f-3b7f37f3 b130ecb8-1410f10 6025934e-3f4a17df d175604-5e83fd66 9e14c724-3f4a17df d5bf8633-3f4a17df 8303c047-65bced95 bd007046-3f4a17df 47e5d3db-3d47f4f4 77207729-e0e232cc f0a371b8-65bced95 776de70c-e0278d3d 19c1fdaf-ca7d8d80 39fa6d3e-f23d1dea 3042ad4b-ca7d8d80 44c96c7b-7968b21c 68812885-f23d1dea 684d1cdf-51126808 b684f56f-65bced95 287f29ba-2f17bce8 c561a755-65bced95 8efbe452-b10c8955 28bf4731-35ded52b a460d5bc-2723bee0 29003132-bb10765b 176d07dc-c518e03e 4429ef9e-ec2cd91b 93731dca-86f8c66a 81328e71-3f4a17df e34691ba-86f932ec 9e5c75f1-fff58f2c 146193c5-9a9a33a4 b2972962-9d973641 f79cb77b-3f4a17df 23a898eb-c40fe774 d1d8d202-db9e7dc4 4ea303a6-3d47f4f4 12be2281-3f4a17df d92562a9-8aa4a421 f66ea88e-4eb6d224 118a869f-c306c9a2 1aecb842-3f4a17df 4932440-d21eb72d 65a86f01-ca7d8d80 b2f0086-870290a7 ef25c1eb-f23d1dea 4bc337ce-a6528b4d db5efd10-88e62167 9a2f4e5b-bad9a271 3ac60855-3ec2a267 4442aae2-75cb33fc ed1d377-e1cc0f14 75f0f0a0-a5822863 e7e71889-4ad60575 f5fff3a2-f23d1dea bbb8f811-3f4a17df 11d91db8-f23d1dea 828a5926-8f2c913 9cade933-f23d1dea 64fbb017-cf4f6ead
,
Sep 29 2017
Experiments: AndroidSigninPromos-Enabled AppBannerTriggering-Control AsyncDns-Control AutofillFieldMetadata-Enabled AutofillRationalizeFieldTypePredictions-Default BackgroundTracing-default BrowserScheduler-AllTasksUserBlocking CSSExternalScanner-Enabled_ScanOnly CheckerImaging-Control2 ChromeChannelCanary-Enabled ChromeHome-Forced_Enabled_Dogfood ChromeHomeDestroySuggestions-Enabled ClearOldOnDemandFavicons-Enabled ContentSuggestionsDebugLog-Enabled_Dogfood CopylessPaste-Enabled DataCompressionProxyHoldback-Disabled DataCompressionProxyPromoVisibility-EnabledWithSnackbarPromo DataReductionProxySiteBreakdown-Enabled_Dogfood DynamicExpectCT-DynamicExpectCTEnabled FixDocumentLeakInAutofillAgent-Default FreedObjectTracker-Control HTTP2-Default KeepAliveRendererForKeepaliveRequests-Enabled_20sec LoadingWithMojo-Control MarkNonSecureAs-show-non-secure-passwords-cc-ui MidiManagerDynamicInstantiation-Enabled_Dogfood NTPArticleSuggestions-Enabled62-FCS_Dogfood NTPBreakingNewsPush-Enabled_Dogfood NTPCondensedLayout-CondensedLayoutWithoutLogo NTPFaviconsFromNewServer-Enabled512 NTPLessThanEightMostLikelyTilesDevCanary-FourOrMoreMLTiles NTPMostLikelyFaviconsFromServer-EnabledInclIOS_Dogfood NTPPopularSites-EnabledGoogleSearchExperiment_Dogfood NTPUseDdljsonApi-Control62 NetworkQualityEstimator-Control4 NewPhotoPicker-Enabled OfflinePagesPrefetchingSuggestions-Control_50_Percent OmniboxBundledExperimentV1-Dev_Android_PhysWebAndNewOmniboxAnswerTypes_Dogfood OmniboxCombinedSpeculativeServiceWorker-PrewarmingWithServiceWorker OmniboxPlaceholderExperiment-Unused PasswordGeneration-Enabled PersistentHistograms-Enabled50 PreviewsClientLoFi-Enabled_2G_Replace_Server_Placeholders_Dogfood QUIC-Disabled ReportingAPI-Enabled ResourceLoadScheduler-Enabled_bg_limit_16 SafeBrowsingUseLocalBlacklist-Use3PAPI SearchLiteDataSaver-Experiment_Dogfood ServiceWorkerScriptStreaming-Enabled SimpleCachePrefetchExperiment-Prefetch32K SpeculativeResourcePrefetchingValidation-Default SubresourceFilter-Control_Dogfood SyncUSSAutocomplete-Control TLS13Variant-Experiment3 TabManagementExperiment-Elderberry ThrottleDelayable-MaxDelayable12_Weight2 UMA-Population-Restrict-dogfood UMA-Uniformity-Trial-10-Percent-group_07 UMA-Uniformity-Trial-100-Percent-group_01 UMA-Uniformity-Trial-20-Percent-group_04 UMA-Uniformity-Trial-50-Percent-default UseMojoAudioOutputStreamFactory-Control V8ContextSnapshot-Enabled VsyncAlignedInput-Control WebFontsInterventionV2-Control-1 WheelScrollLatching_AsyncWheelEvents-Control XGEOVisibleNetworks-Experiment
,
Sep 29 2017
ktam@, by "Chrome Dev", do you mean 63.0.3223.7 (which is the current recent dev vesrion)? The suggestions content is there immediately, but the sheet open does look pretty laggy.
,
Oct 2 2017
Correct. I mean 63.0.3223.7.
,
Oct 2 2017
One thing we can try here is delaying the toolbar button animation when the sheet is opened since that causes a requestLayout() call. If we stagger the things that are happening on sheet open, we may be able to reduce some of the lag.
,
Oct 4 2017
,
Oct 4 2017
A quick update here - Kingston tried disabling a number of experiments to no avail. We are unable to reproduce anywhere besides Kingston's Canary. Kingston was planning to retest on a future Canary push. Perhaps this is caused to some poor interaction of active experiments. Bernhard, are any of the NTP experiments in #2 new?
,
Oct 4 2017
+ktam@ to provide more details on experiments he disabled and whether this is still reproducing on current Canary
,
Oct 7 2017
I disabled all the experiments under NTP and favicon to no effect. The lag is less severe in the current Canary though still noticeable when compared to Dev. (it's <100ms freeze)
,
Oct 9 2017
These are all of the chrome://flags experiments that I see related to the NTP/favicons/suggestions. By "all the experiments", do you mean all of these or different set? - Show popular sites for the New Tab page - Breaking News Push - Make New Tab Page Snippets more visible - Enable Contextual Suggestions - Get favicons for content suggestions from a new server - Download favicons for NTP tiles from Google - Show also lower resolution favicons in NTP tiles - Large thumbnails layout for content suggestions cards - Use content suggestions thumbnail dominant color - Load favicons from Web Manifests (I don't think this affects Zine) - Show server-side suggestions on the New Tab page - Show assets downloads on the New Tab page - Show offline page downloads on the New Tab page - Show recently visited bookmarks on the New Tab page - Show recent foreign tabs on the New Tab page - Notify about new content suggestions available on the New Tab page - Condensed NTP layout - Condensed NTP tile layout - Site Exploration UI - Google G in the New Tab page omnibox - Enable NTP offline pages - Disable minimumfor server-side tile suggestions on NTP - Keep prefetched content suggestions - Default content suggestions category order - Content suggestions category ranker - Use new ddljson API for Doodles I expect many of these don't affect Chrome Home and/or have been on for a long time, but I'm not familiar enough with any of them to know for sure.
,
Oct 9 2017
Another thing you could try if your device is connected to a desktop/laptop is to open chrome://inspect/?tracing, which lets you run remote tracing on the device, so we could try to see where the jank is coming from.
,
Oct 9 2017
mdjones@ did tracing on Kingston's phone, and it provided no useful information. It showed the gap, but no useful information. We tried putting a debug build on Kingston's phone to get more useful information and the debug build din't present the problem.
,
Oct 10 2017
Hmm.. I can no longer repro this as I migrated to a new phone and apparently canary app data wasn't transferred over. Closing out until we get another repro case. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by k...@chromium.org
, Sep 29 2017