Stop loading current page when omnibox is active (on low-end devices) |
||||
Issue descriptionLet's optimize the following use case on low-end Android devices: 1. Chrome is started 2. It starts reloading last opened tab 3. User taps omnibox to search for something 4. Keyboard appears, user starts typing This scenario is currently very laggy on 512 low-end device, because keyboard fights with renderer that loads in the background. Can we pause loading in this case to free CPU / memory for the keyboard?
,
Aug 18 2017
,
Aug 18 2017
The renderer scheduler is pretty flexible here. We could fairly easily block just loading tasks, or all tasks.
,
Aug 18 2017
Can we prioritize instead of blocking, so the keyboard gets all the resources it wants? We definitely wouldn't want to block background loading on omnibox focus on devices where the keyboard wasn't laggy, and I'm not 100% convinced we can determine this based on a simple device capabilities check. Seems like the OS scheduler ought to be able to deal with this given sufficient priority info, but maybe I'm wrong?
,
Aug 21 2017
Could you please record a systrace of this scenario? If the omnibox is being laggy because the background renderer is stealing CPU time then it feels like we should try adjusting thread/process priorities. If the lag is caused by some other activity in the browser process (perhaps triggered by the renderer) then we need something smarter.
,
May 8 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dskiba@chromium.org
, Aug 18 2017