Lazy load downloads history |
|||
Issue descriptionCurrently each time a new download starts, the entire downloads history is loaded into memory. This is wasteful since most users on desktop don't open chrome://downloads and hence won't even see the list of downloads. Instead, let's not load the entire downloads history each time DownloadManager is created. If we want to query a specific subset of downloads, then we should do so using the downloads history DB selectively. Downloads queries should be made against the history DB. chrome://downloads should pass the memory cost of keeping downloads history around into the renderer process hosting the chrome://downloads page. I.e. aside from active downloads, all other downloads are passed through the browser without being retained.
,
Jun 23 2016
It does. Currently automatic resumption requires loading the entire downloads history, which is a waste. We only need to restore the resumption candidates.
,
Dec 21 2016
,
Mar 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 22 2018
Probably beyond this, we want to see if we can just not keep the history in memory *at all*. This would require asynchronous access to the APIs. If this isn't feasible we can see if we can only load a small amount of memory for each download instead of the full item. |
|||
►
Sign in to add a comment |
|||
Comment 1 by cbentzel@chromium.org
, Jun 22 2016