755415 - Partial page blur/low-res on waking device from sleep

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Richard Newman [:rnewman]]

Attachment: Screenshot

Phone was off. Got a text message, so woke device to this: see attached screenshot.

Scrolling returns page to sharpness.

Comment 1

[Richard Newman [:rnewman]]

This is on first released beta, HTC EVO 4G, Android 2.3.5.

Comment 2

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

qawanted to try to get STR. Some possible ways I can think of that might trigger this is if you fling the page and then either lock the screen or switch apps or something while the page is still flinging. Once fennec is deactivated we have some code that stops the compositor from compositing because we don't have a GL context anymore, and we also stop drawing around that time. The fling, however, should keep going until it runs out on its own. It could be that once we reactivate we don't have the final area painted so we fall back on the low-res screenshot which results in this.

Comment 3

[Adrian Tamas (:AdrianT)]

I was able to reproduce the issue on planet.mozilla.org by fast scrolling and the minimizing Fennec. Sometimes the low resolution screenshots are repainted correctly but sometimes the pages remain in low resolution. This is easier to reproduce on Motorola Droid Pro ( Android 2.3.4) or Samsung Captivate (Android 2.2) but I was able to reproduce the issue on Samsung Galaxy Nexus (Android 4.0.2) and HTC Desire Z (Android 2.3.3). The HTC Desire Z also experienced a few different issues covered by bugs: Bug 754253 and Bug 756038.

Steps to reproduce:
1. Load planet.mozilla.org and wait for page to finish loading.
2. Flick scroll fast a few times.
3. Before rendering finishes minimize Fennec using the "home" button.
4. Maximize Fennec again.

Video captures from HTC Desire Z and Motorola Droid Pro: http://youtu.be/lASPLzCyQdk, http://youtu.be/VoZriGMJq-Q

I will continue to try and get more reliable steps to reproduce.

Comment 4

[Adrian Tamas (:AdrianT)]

Attachment: log Motorola Droid Pro

Comment 5

[Adrian Tamas (:AdrianT)]

Attachment: logs Samsung Galaxy Nexus

Comment 6

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

CC'ing ajuma and vlad who have been working in this code recently; the logs show invalid surface errors.

Comment 7

[Ali Juma [:ajuma]]

If scrolling returns the page to sharpness (as in Comment 0), it's probably not an invalid surface problem but rather that we're failing to trigger a paint event in this situation.

For the situations described in Comment 3, where we seem to get into a bad state and stay there, using an invalid surface could indeed be the problem. It's possible that Vlad's patch in Bug 752368 (which ensures that we absolutely do not make GL calls after the surface is destroyed) fixes this. 

Adrian, can you still reproduce with this build: http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/[e-mail]-0e539f1d4ce4/try-android/fennec-15.0a1.en-US.android-arm.apk

Comment 8

[Adrian Tamas (:AdrianT)]

Using the try build for Comment 7 on Motorola Droid 2 the page gets eventually repainted. The most time I saw the page remain in low-resolution mode was ~10-15 seconds but was repainted after. Please see : http://youtu.be/Ean1_U8Pwk8

Comment 9

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.