reloading img src will create infinite number of cached assets in dev tools
Reported by
bill.ch...@gmail.com,
May 7 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30 Steps to reproduce the problem: 1. Fetch the enclosed file from a web server (requires two fetchable svg files). 2. Open Chrome dev tools, Application tab, Frames > Images. 3. Watch the cached images increase, one per second, until page is reloaded. What is the expected behavior? Other browsers (e.g. Safari) do not cache all loaded images indefinitely What went wrong? We produce long-running web apps, loading many images into page elements without refresh. The Chrome dev tools cannot deal with this. The browser window itself seems untroubled: heap does not grow. Did this work before? No Chrome version: Version 57.0.2987.133 (64-bit) Channel: stable OS Version: OS X 10.12.4 Flash Version: This example illustrates the issue: img.src inline with assets loaded from a server. Under this scenario we were able to reliably and robustly reproduce the behaviour.
,
May 18 2017
As this issue triaged from webserver , could anyone from MTV team please look into this issue. Thanks..!!
,
May 19 2017
Eugene, please take a look.
,
May 19 2017
,
May 24 2017
Application tab, Frames > Images is showing resources fetched by a web page. In this case each time loadImageOne/loadImageTwo a new "resource" is fetched. Even though Chrome fetches it from a cache (as is reflected on the Network tab), the resource is a new one for the Application tab purposes. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, May 12 2017