Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Critical Request Chain size info is incorrect #2597

Closed
mflodin opened this issue Jun 26, 2017 · 0 comments
Closed

Critical Request Chain size info is incorrect #2597

mflodin opened this issue Jun 26, 2017 · 0 comments
Assignees
@ebidel

Comments

@mflodin
Copy link

mflodin commented Jun 26, 2017

There seems to be some issue with the sizes listed under Critical Request Chain. They are all listed as having the same size, and don't seem to match any of the actual sizes.

Issue found in the built-in Lighthouse in Chrome Canary 61.0.3141.0 (64 bits) on Windows. Also found in Chrome Canary on OSX, but not sure which exact version.

Issue also exists in the Chrome Extension of Lighthouse (Version: 2.1.0).

Seems to have been working properly back in February at least as can be seen in #1729

screen shot 2017-06-22 at 10 35 29
screen shot 2017-06-22 at 11 01 41
@mflodin mflodin mentioned this issue Jun 26, 2017
Closed
@ebidel ebidel self-assigned this Jun 26, 2017
ebidel added a commit that referenced this issue Jun 28, 2017
@ebidel
CRC audit: child chain renders using its own transfersize. Fixes #2597
316514b
@ebidel ebidel mentioned this issue Jun 28, 2017
Merged
ebidel added a commit that referenced this issue Jun 28, 2017
@ebidel
CRC audit: child chain renders using its own transfersize. Fixes #2597
2abc66f
ebidel added a commit that referenced this issue Jun 28, 2017
@ebidel
CRC audit: child chain renders using its own transfersize. Fixes #2597 (
673c3ba 
#2610)

* CRC audit: child chain renders using its own transfersize. Fixes #2597

* comment

* blah
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ebidel ebidel

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebidel @mflodin