Tested the issue in Android 7.0 and able to reproduce the issue. 

Steps Followed:
1. Launch Chrome.
2. Navigated to naver.com
3. Change to landscape mode and Observed bad text visibility(Text is pixelated)

Chrome versions tested:
67.0.3396.87(Stable), 69.0.3464.0(Canary)

OS:
Android 7.0.0

Android Devices:Samsung S7

Using the per-revision bisect providing the bisect results,
Good Build - 66.0.3341.0 (534605)
Bad Build - 66.0.3342.0 (534887)

You are looking for a change made after 534605(GOOD), but before 534606(BAD).

https://chromium.googlesource.com/chromium/src/+/9d94df31c926ba5e8f02f85e88686ee1482cf560

@Bill Budge : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned.

Please navigate to below link for log's and screen cast --
go/chrome-androidlogs/853109

Thanks!

Sorry, I have no insight on the cause of this. My change only affects unittests (no changes to shipping Chrome/WebView code on any platform.)

Could you retry the bisection? Remarking as Untriaged, and needs an owner. I would suggest a GPU or Blink person.

As per comment #4, Bisected again. Below are the details:

Using the per-revision bisect providing the bisect results,
Good Build - 66.0.3322.0 (529187)
Bad Build - 66.0.3324.0 (530027)

You are looking for a change made after 529610(GOOD), but before 529611(BAD).

https://chromium.googlesource.com/chromium/src/+/97414c7ab5cfc16a9e672de768754279e4ca5720

@Adrienne Walker : Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned.

Please navigate to below link for log's and screen cast --
go/chrome-androidlogs/853109

Thanks!

typo @ Good and Bad builds:
Good Build - 65.0.3322.0 (529187)
Bad Build - 65.0.3324.0 (530027)

Thanks!

Hmm, I landed a followup for a similar bug in https://chromium-review.googlesource.com/883944 which got merged back to m65.  I suppose that doesn't address this issue though if it is also having trouble.

I should be able to get an S7 by Friday and can take a look then.

Thanks for the update. Since this is a recent regression, it would be great to have a fix for M68/ M69.

This will not block this week's M68 Beta.

I cannot make this repro on ToT Chrome (r570807) on a Galaxy S7 (SM-G930F with a Mali-T880).  Attached are pictures of this looking correct.

Is there anything else I need to do to repro this?

Deleted: Screenshot_20180627-132531_Chromium.jpg 497 KB

	Screenshot_20180627-132531_Chromium.jpg 497 KB View Download

Deleted: Screenshot_20180627-132540_Chromium.jpg 464 KB

	Screenshot_20180627-132540_Chromium.jpg 464 KB View Download

Just to be sure, I tried a chromium build at 530033 and could not reproduce it either on the same device.

Does anybody have any extra hints on how to reproduce this?

Not able to repro text issue being Pixelated;
Device: Samsung Galaxy A5 / NRD90M
Android Versions: 68.0.3440.40 & 69.0.3480.0

1. Open the url 'naver.com' in Chrome.
2. Rotate to landscape mode.

Only issue i see is a gray blan area on the left side of the screen.

Please find uploaded screen-record @
https://drive.google.com/corp/drive/u/0/folders/1ZrOZoRDQNn2TXI4UVSmu7NNRsifR5f7W

jbanavatu@ are you still able to reproduce this issue?

Tested on chrome version 67.0.3396.87 , 69.0.3486.0 using samsung galaxy s7 and Unable to reproduce this issue .

Thanks!

Deleted: 853109.png 403 KB

	853109.png 403 KB View Download

Dear Chrome team

Please see the description and note that this issue depends on GPU.
It is still reproducible on 67.0.3396.87 using Samsung Galaxy S7 (Mali-T880) and Samsung Galaxy A5 (Mali-T830).
All models using the Mali-T880 / Mali-T830 reports this issue.

Thanks.

Somehow we are unable to reproduce this issue. Tested on 67.0.3396.87 using samsung s7 (with GPU Mali-T880).
Please refer to the screen-cast attached.

Thanks!

Please refer to the screen-cast attached.

Thanks!

Deleted: 853109_notrepro.mp4 5.1 MB

	853109_notrepro.mp4 5.1 MB View Download

enne@ are you looking into this issue? M68 release is next week.

No, I am not looking into this issue.  I cannot reproduce it and neither can jbanavatu.

I am going to give this one last try today and see if I can bisect and verify that the followup change I listed above addressed this issue in the past.

Unless there are more precise instructions on how to reproduce, I don't think there's much else I can do at the moment.

Bisected this manually most of the way, and found 531643 was bad, while 531659 was good.  This is why this doesn't repro on ToT or 67.

As I suspected, https://chromium-review.googlesource.com/883944 is likely why this got fixed, that I mentioned in comment #8.

Closing this bug as WontFix.

Dear Chrome team

It's reproducible in O OS not N OS.
Could you please check if it's reproducible on O OS device using GPU "Mali-T830" and "Mali-T880"?

All of my testing is on Oreo.  I think comment #22 still stands.  This was broken in 529611, and fixed in 531658.

enne@ could you let me know which version has a fix so that I will be able to test it?
What you meat by 531658 was it's fixed on 57.0.5316.58?

It should be in any version later than 65.0.3325.49.