Transfer size equals to content size only happens on first item in network panel of DevTools
Reported by
ro...@iworm.net,
Jan 8 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce the problem: 1. Open DevTools and switch to network panel. 2. Click "Use large request rows" icon, so there will show "Transfer Size" and "Content Size" in "Size" column. 3. Open http://news.163.com or any other websites. 4. After all contents are loaded. Please look at the "size" column. 5. You will find the two size are equal, and this will only happens to the first item. All others has different "Transfer Size" and "Content Size". 6. Check the response of the first item, you will find the content encoding is set to gzip, so the two size should not be equal in most of cases. What is the expected behavior? "Size" column displays the correct transfer size. What went wrong? Only the first item in network panel displays the wrong transfer size. Did this work before? N/A Chrome version: 63.0.3239.132 Channel: stable OS Version: Ubuntu 17.10 Flash Version:
,
Jan 8 2018
Able to reproduce this issue on reported version 63.0.3239.132 with steps mentioned in comment#0. But not reproducible on beta 64.0.3282.71 and canary 65.0.3315.0 using Windows10, Ubuntu 14.04 and Mac 10.13.1. Hence providing reverse bisect info. Last Bad Build: 64.0.3267.0 First Good Build: 64.0.3268.0 You are probably looking for a change made after 516011 (known good), but no later than 516012 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/98e533d332344ee7fdf2cace842c61b25b4a2020..81f89b3b8fbb90742d88ffef7d82a561cfee3c5b Reviewed-on: https://chromium-review.googlesource.com/744290 Suspecting same from changelog. @caseq: Please confirm the bug and help in re-assigning if it is not related to your change. Adding RB-Stable for M-63. Please remove if not the case. Thanks!
,
Jan 16 2018
We're not planning any further M63 releases. Per comment #2, this is fixed in M64, correct?
,
Jan 16 2018
roger@, Next M64 stable release will have this fix which is going to happen very soon. Please feel free to update the thread if you still see any issues after M64 stable release. Thank you! |
||||
►
Sign in to add a comment |
||||
Comment 1 by ro...@iworm.net
, Jan 8 2018