828995 - Regression: Blurry content on first page-load

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Toolbar, defect)

Description

[Aaron Train [:aaronmt]]

Attachment: Nightly (01/10) - Screenshot

These past few days on mozilla-central (mozilla-20/21) I have occasionally started seeing content that will load blurry (even our 404 page) and will only adjust itself on zoom or scroll. 

Has anyone else started seeing this?

Are there any recent related checkins that might have touched unearthed this?

This is on my Note II and Galaxy Nexus.

Example URL, I just loaded Google Mail and am seeing this; see screenshot.

Comment 1

[Kartikaya Gupta (email:[e-mail])]

I haven't really noticed this. A regression range would be good to have.

Comment 2

[Aaron Train [:aaronmt]]

Attachment: Nightly (01/10) - Screenshot

about:privatebrowsing

Unfortunately wasn't paying attention to what I was playing around with. Will post if I do.

Comment 3

[Aaron Train [:aaronmt]]

Attachment: Nightly (Bing.com)

I can reproduce this rather consistently with the first URL I visit after a new profile on my Galaxy Nexus (Android 4.2). I just create a new profile, launch fennec and visit http://bing.com

Comment 4

[Aaron Train [:aaronmt]]

Attachment: Nightly (01/21) - Google

Kind of surprised nobody else is seeing this?

Comment 5

[Brad Lassey [:blassey] (use needinfo?)]

(In reply to Aaron Train [:aaronmt] from comment #4)
> Created attachment 704629 [details]
> Nightly (01/21) - Google
> 
> Kind of surprised nobody else is seeing this?

Aaron, if you can reproduce consistently, can you get a regression range?

Comment 6

[Aaron Train [:aaronmt]]

If I could that would be in here.

Comment 7

[Aaron Train [:aaronmt]]

I found some steps to reproduce

Create a new profile, launch Fennec


i) Head to http://www.apple.com, and let the site load
ii) Head to http://m.globeandmail.com (404), I get the same blurry content on our Server Not Found page

Comment 8

[Aaron Train [:aaronmt]]

I am hitting this again on today's Nightly on my SII

D/GeckoLayerClient( 5498): Aborting update due to viewport not in display-port

STR: 

Open a new private tab
Rotate to landscape
Rotate to portrait

Comment 9

[Aaron Train [:aaronmt]]

E/GeckoConsole( 5498): Warning: setDisplayPort resolution did not match zoom for background tab!
E/GeckoConsole( 5498): Warning: setDisplayPort resolution did not match zoom for background tab!
D/skia    ( 5498): --- SkImageDecoder::Factory returned null
I/SurfaceFlinger( 1812): id=440 Removed FreezeSurface idx=10 Map Size=5
I/SurfaceFlinger( 1812): id=441 Removed BlackSurface idx=6 Map Size=5
I/SurfaceFlinger( 1812): id=440 Removed FreezeSurface idx=-2 Map Size=5
I/SurfaceFlinger( 1812): id=441 Removed BlackSurface idx=-2 Map Size=5
I/SurfaceFlinger( 1812): id=442 Removed BlackSurface idx=6 Map Size=5
I/SurfaceFlinger( 1812): id=443 Removed BlackSurface idx=6 Map Size=5
I/SurfaceFlinger( 1812): id=442 Removed BlackSurface idx=-2 Map Size=5
I/SurfaceFlinger( 1812): id=444 Removed BlackSurface idx=6 Map Size=5
I/SurfaceFlinger( 1812): id=443 Removed BlackSurface idx=-2 Map Size=5
I/SurfaceFlinger( 1812): id=444 Removed BlackSurface idx=-2 Map Size=5
V/WindowManager( 1968): rotationForOrientationLw(orient=-1, last=0); user=0  mLidOpen=-1 mDockMode=0 mHdmiPlugged=false mAccelerometerDefault=1 sensorRotation=0
D/GeckoLayerClient( 5498): Aborting update due to viewport not in display-port

Comment 10

[Kevin Brosnan [Ex-Mozilla]]

I can reproduce the rotation blurriness on about:privatebrowsing rotation using a Nexus S running Android 4.0.4 about 1 in 4 times.

Comment 11

[Chris Lord [:cwiiis]]

Sounds like either incorrect viewport metrics or missing draws, the latter of which could be caused by bug 842389... Let's fix that first and revisit this.

Comment 12

[Kevin Brosnan [Ex-Mozilla]]

I was using the 27th build for my comment.

Comment 13

[Kevin Brosnan [Ex-Mozilla]]

Aaron I can't repro comment 8 any more. How about you?

Comment 14

[Aaron Train [:aaronmt]]

Neither can I, using my SII and Galaxy Nexus and not able to reproduce anymore. Marking resolved via bug 842389.