|
|
I've just started using Chrome, as I suspected IE 11 on Win 8.1 may have been crashing my system several times a day. (It's either that or NetWorx it seems, as I ditched both last night and have had no trouble since).
See this page, which is fine in IE 11 which I have run a couple of times just to check the page .
In Chrome the main photos in the article are completely pixellated and almost totally unrecognisable. The smaller pictures lower down the right-hand side are perfect, but the higher ones there which are versions of the main ones are also junk.
Is this sort of thing common with Chrome?
Edited by RobertoS (Wed 20-May-15 18:09:14)
|
|
|
I use FF most of the time but had a look at the link in Chrome and it's issue free, using Windows 8.1 (haven't installed the very latest updates yet).
plusnet user
|
|
|
Hmmm  .
I'll try a cold boot.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
That made no difference. Cleared browsing history and image cache, tried with lower screen resolution (normal is the maximum 3840 x 2160). Chrome and Windows both up to date.
I'm using desktop mode, but the same happens in Windows mode.
|
|
|
I'm seeing the same in Chrome (Version 43.0.2357.65, which About says is the latest) on a Mac, but not in Chromium or Safari.
I tried turning hardware acceleration off, but that made no difference. Dunno
|
|
|
No problems with Chrome in Windows 7 running at 1920 x 1080.
I've tried it with both Version 44.0.2403.4 dev-m (64-bit) and Version 45.0.2407.0 canary (64-bit).
Plusnet Unlimited Fibre Technicolor TG582n , St Ives Cambs (EMSTIVE)
|
|
|
Mine says Version 43.0.2357.65 m.
But thanks.
|
|
|
Thanks. Just tried that resolution because of your post. Just the same, and text is fuzzy.
|
|
|
Not sure what the "m" means� I right-clicked a pixellated image and saved it, loaded it into a viewer and it was fine so it's a rendering problem not a corrupt download.
You could try the Report an issue button on the About page...
|
|
|
Seeing the following in chrome Version 43.0.2357.65 m on Windows 7 Pro (64bit)
Seems its Chroma subsampling its having issues with.
Ok, I just saved the JPG Image and opened it up in an image app and resaved it.
*** New Saved version that works in Chrome ***
Lewis-Hamilton-578422b.jpg
Image
Format : JPEG
Width : 590 pixels
Height : 350 pixels
Chroma subsampling : 4:4:4
Bit depth : 8 bits
Compression mode : Lossy Whereas this original one doesn't
Lewis-Hamilton-578422.jpg
Image
Format : JPEG
Width : 590 pixels
Height : 350 pixels
Chroma subsampling : 0:4:4
Bit depth : 8 bits
Compression mode : Lossy Both images work in IE fine.
Paul
|
|
|
Thanks Paul, I've just done the same, and as you say that works. Just got to work out a way to explain in the report to them on their form.
|
|
|
See reply to PaulKirby Bill, thanks  .
|
|
|
Report sent.
Thanks to all who contributed  . It's good to know others also see it, before reporting it. Plus I added to my diagnostic skills - save the mess and see if it works elsewhere! That saving and displaying is mentioned in my report.
|
|
|
Try a right click on the Chrome desktop shortcut icon, then a click on properties and then the Compatibility tab, then the Run compatability troubleshooter to see if it helps.
http://postimg.org/image/5jbujpbjh/
plusnet user
|
|
|
OK, tried that.
Compatibility was set to Win 8 but ticking it made no difference. Swapping it to Win 7 crashed it a few seconds after loading.
Disabling display scaling when using high DPI didn't help.
Running the Troubleshooter, when I reply it still isn't displaying correctly it tells me to report it to Microsoft. LMAO!
|
|
|
So it does, what a mess! Version 43.0.2357.65 m (64-bit) on Windows 10 Technical Preview. I've never experienced this before with Chrome.
Kevin
plusnet Unlimited Fibre - sync approx 65000/20000 at 450m - BQM
Using OpenDNS
Domains and web hosting with TSOHOST
|
|
|
Image
Format : JPEG
Width : 590 pixels
Height : 350 pixels
Chroma subsampling : 0:4:4
Bit depth : 8 bits
A quick Google suggests 0:4:4 is not a valid value. Maybe the error handling for invalid values has been altered in Chrome.
Oliver.
|
|
|
Image
Format : JPEG
Width : 590 pixels
Height : 350 pixels
Chroma subsampling : 0:4:4
Bit depth : 8 bits
A quick Google suggests 0:4:4 is not a valid value. Maybe the error handling for invalid values has been altered in Chrome.
I think you have to flip them round to produce 4:4:0
Paul
|
|
|
Pictures on that page are perfect here on Chrome Version 42.0.2311.152 m. Windows 10 build 10074.
|
|
|
Pictures on that page are perfect here on Chrome Version 42.0.2311.152 m. Windows 10 build 10074.
Yep, version 43 introduced the issue. I had to update Chrome to replicate it.
Oliver.
|
|
|
Quite neat that  . Beta Windows and out-of-date Chrome  .
/runs and hides.
|
|
|
Yes, but it works, or at least it did until I upgraded a few minutes ago, which is probably a vote for 'If it ain't broke, don't fix it' lol
|
|
|
Oooops!
But you were warned.
I didn't realise you had catlike tendencies. (CKTC)
|
|
|
I was on 42.0.2311.152 m and the pictures were fine. I had to go into About to get the version number and Chrome helpfully updated itself to 43.0.2357.65 m - bang, pixellated pictures
They are fine in 45.0.2407.0 canary, Chrome tells me I was up to date with that.
Virgin Cable (100/6) + EE Mobile BB
|
|
|
Oooops!
But you were warned.
I didn't realise you had catlike tendencies. (CKTC)
I have all sorts of tendencies. One of which is considering a warning a challenge
|
|
|
Exactly what happened to me. No choice, or warning!
|
|
|
and no way to go back either...
Virgin Cable (100/6) + EE Mobile BB
|
|
|
|
Good find....
|
|
|
Is it happening a lot, or just that page?
I expect they'll put out a fix, if it is doing.
|