New issue
Advanced search Search tips

Issue 600110 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Images fuzzy on certain websites + CPU spikes upon first opening Chrome + on certain image-laden websites

Reported by rangerws...@gmail.com, Apr 2 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2696.0 Safari/537.36

Example URL:
see "What went wrong"

Steps to reproduce the problem:
1. Opened Chrome
2. Opened mentioned websites
3. 

What is the expected behavior?
Normal resolution/non-pixellated images.

CPU usage normal.

What went wrong?
1.  Images fuzzy/pixelated/off-color/low-resolution on certain websites/pages such as Google Images, Reuters, CarDomain, etc.  Other websites, e.g. Instagram everything working normally.

2.  CPU spikes to 100% upon first opening Chrome Canary +  nearly as high on opening image-intensive websites/pages such as the aforementioned.

Problem persists even with all extensions & plug-ins, e.g. Shockwave Flash 21.0 disabled.  

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Up until Wednesday.  

Does this work in other browsers? No Firefox

Chrome version: 51.0.2696.0  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0
 
FUZZY IMAGES - GOOGLE IMAGES.JPG
193 KB View Download
FUZZY IMAGES 3.JPG
96.8 KB View Download
FUZZY IMAGES 4.JPG
111 KB View Download
FUZZY IMAGES 2.JPG
140 KB View Download
FUZZY IMAGES.JPG
120 KB View Download

Comment 1 by kojii@chromium.org, Apr 6 2016

Cc: kojii@chromium.org
Labels: Needs-Feedback
Thank you for the report. However, I cannot confirm the fuzzy images at:
https://www.google.co.jp/search?q=porsche+911&tbm=isch

Could you confirm it still occurs, and if so, post other URLs?
A few random sites where I'm finding images are blurry/pixelated/low-res.

www.cbc.ca
www.livestrong.com
www.taquitos.net
www.cbssports.com
m.mlb.com
www.men'shealth.com
io9.gizmodo.com
ca.oakley.com
www.prevention.com
www.NFL.com

Whereas images on:

Imgur.net
Gawker.com

are fine.

Comment 3 by kojii@chromium.org, Apr 8 2016

Cc: bunge...@chromium.org
Components: -Blink Internals>Skia
I can't see differences of images in the sites mentioned in comment #2 between Canary and IE.

bungeman@, any ideas?
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 8 2016

Labels: -Needs-Feedback Needs-Review
Owner: kojii@chromium.org
Thank you for providing more feedback. Adding requester "kojii@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Instead of posting jpg (which is lossy and effectively introduces blur) please post screen captures as png (which is not lossy and will preserve the effect being described). There are a number of places where things could have gone wrong here, but it's not clear from the images in the report exactly what is actually being displayed due to compression artifacts from the jpg encoding. If you can post a few screen captures saved as png, it may be helpful.

That being said, are you on a high resolution device? I've tried briefly reproducing with Canary 51.0.2703.0 and don't see anything out of the ordinary on the above sites. If you update the Canary does that change anything?

Comment 6 by kojii@chromium.org, Apr 8 2016

Labels: -Needs-Review
The problem has been solved.  It actually turned out to be a data
compression issue with the VPN I'm using.

Thanks for your help.
Status: WontFix (was: Unconfirmed)
I'm glad you figured out what was going on. I have to close this as 'WontFix', but I wish we had a closed status more like 'TurnedOutToBeSomethingElse'. I've had a few of those lately.
Well if anyone asks I'll be sure to attribute my issue correctly to my own
stupidity vs. anything actually wrong with Chrome :).

Sign in to add a comment