Fail to load response data in network inspection panel when a page is loaded and then jumps to other page quickly.
Reported by
x.gow...@gmail.com,
Jul 12 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 Steps to reproduce the problem: 0. The test page test.html and test2.html mentioned below are attched in the end, please download and then host them on the web that can be visited directly via Chrome (such as http://localhost/test.html) instead of using the file:// straightforward. 1. Open a new blank tab in case of any interference. 2. Open Developer Tools. 3. Turn to the Network tab, and check "Preserve log" option. 4. Visit the test.html (such as http://localhost/test.html) via the address bar. 5. Repeat 1, 2, 3 and visit test2.html via the address bar. What is the expected behavior? The Network tab in Developer Tools records all data and exhibit them normally. And the content in the requested file can be found in the corresponding record entry "test.html -> Response". What went wrong? For test2.html, there is no response body recorded in "Network -> test2.html -> Response", and it reads "Failed to load response data". Besides, I notice that whether the response body is recorded normally is associated with the residence time on page. Did this work before? Yes I got this problem at least in Chrome 49.x. Chrome version: 51.0.2704.106 Channel: stable OS Version: Flash Version: Shockwave Flash 22.0 r0
,
Nov 22 2016
It seems that this problem has existed for so long time and they will continue to ignore this bug. https://bugs.chromium.org/p/chromium/issues/detail?id=141129
,
Jul 20 2017
This happens because the target the request was made in no longer exists and when we ask for the data, there is no data associated because it is no longer in memory. This is done because devtools would be almost unusable on any moderately complex sites if we extracted the response of every request. The compromise was to use blink's memory cache model and ask for the data when needed. So, yes this will likely never be fixed :-( However, if you can request the content before it goes away, it'll persist in devtools until the request gets cleared in devtools :-) |
||
►
Sign in to add a comment |
||
Comment 1 by alph@chromium.org
, Jul 12 2016Status: Assigned (was: Unconfirmed)