1606179 - part of the screen is black during page load

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect, P1)

Description

[Sören Hentzschel]

Attachment: screenshot

https://github.com/mozilla-mobile/fenix/issues/7338:

STR:

1. open a website with Fenix on a device with WebRender enabled

Expected:

No black screen or black part of the screen.

Actual:

Part of the screen is black. It happens on my OnePlus 7T Pro McLaren Edition which has a Adreno 640 GPU.

WebRender was enabled in bug 1602597 for devices with Adreno 5xx and Adreno 6xx GPU in GV Nightly. Should WebRender ride the trains for these devices in GV 73 then this bug should be fixed in time for GV 73, so precautionary making this a dependency for bug 1602532 (wr-73-android).

Comment 2

[Jamie Nicol [:jnicol]]

I can reproduce on my OnePlus 6 (Adreno 630, Android 9).

I believe the black area is where the keyboard used to be. Sören, am I correct in thinking that this only happens when loading a page after typing its address or searching with the keyboard? And that loading a page after clicking a link does not cause this?

This must be related to the other bugs we have to do with black flashes. Maybe we're clearing a white background too early, while the keyboard is still visible. Then when the keyboard is hidden the window is resized and the new area remains black until the first actual paint.

Comment 3

[Sören Hentzschel]

I believe the black area is where the keyboard used to be

On my device the black area is larger than the area where the keyboard used to be.

am I correct in thinking that this only happens when loading a page after typing its address or searching with the keyboard?

I see no way to load a page without enabling the keyboard so yes, it happens after typing its address or searching with the keyboard, but I don't know if it would also happen without the keyboard.

And that loading a page after clicking a link does not cause this?

No, clicking a link does not cause the issue.

And it seems to happen only if I use the address bar from the home screen. Opening the address bar in an active tab and loading a website from there does not cause the issue.

Comment 4

[Jamie Nicol [:jnicol]]

In reply to Sören Hentzschel from comment #3)

On my device the black area is larger than the area where the keyboard used to be.

For me it is exactly the size of the keyboard plus the scan/shortcuts toolbar. If that's not the case for you, then a screen recording of this bug would be extremely helpful!

I see no way to load a page without enabling the keyboard so yes, it happens after typing its address or searching with the keyboard, but I don't know if it would also happen without the keyboard.

One way is to open an item from your history or bookmarks. For me this does not reproduce the bug.

And it seems to happen only if I use the address bar from the home screen. Opening the address bar in an active tab and loading a website from there does not cause the issue.

This is very useful information, thanks. I see the same behaviour. I guess this makes sense if we pause/resume the gecko session when the tab switcher is opened/closed, but not when just typing on the address bar of an active tab.

Comment 5

[Sören Hentzschel]

Attachment: screenrecording.mp4

For me it is exactly the size of the keyboard plus the scan/shortcuts toolbar. If that's not the case for you, then a screen recording of this bug would be extremely helpful!

I attached a screen recording.

One way is to open an item from your history or bookmarks. For me this does not reproduce the bug.

Yes, I can confirm that it doesn't happen from the library.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:jbonisteel, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 7

[Jessie [:jbonisteel] pls NI]

Kris, can you please set a priority for this bug? Thanks!

Comment 8

[Jamie Nicol [:jnicol]]

P1 because we want it fixed for 73. This is fixed by bug 1581868 which has landed, but has not quite made its way in to Fenix Nightly yet. Once it has, and I've verified it works, I'll request uplift and close this bug.

Comment 9

[Jamie Nicol [:jnicol]]

The fix for bug 1581868 has made its way in to Fenix nightly, and I can no longer reproduce this issue.