1626671 - Page rendering gets stuck after opening article and navigating back

Status: RESOLVED MOVED

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

Description

[Kris Taeleman (:ktaeleman)]

I've seen this issue a couple of times, but it's not consistent
sometimes when opening articles on digg.com and going back to the main site
the page will get stuck and you need to switch tabs or so to make it start rendering again
it will actually navigate to different pages in the background, just not show them
I've tried running without WR for a bit and don't notice the same behaviour

STR:

• Navigate to digg.com
• Repeat the following steps:
  ** Open article (will open in new tab)
  ** Press back to go to the main page (digg.com)

Notice how sometimes (1/100?) the article will remain on screen while in the background the page has changed. Switching tabs or apps will fix the issue.

Comment 1

[Kris Taeleman (:ktaeleman)]

@kats: Talked to Jamie about this and our theory is that this happens on sites that open articles in a new tab. going back would close the tab, but keep displaying the closed page.

Any idea where to start on this?

Comment 2

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

I'm not sure if the bug here is related to something else I've seen recently and have been meaning to file but haven't gotten around to yet - when opening a page in a new tab, it used to be that the new tab would come into the foreground right away and then load and render. Now (since sometime in the last two weeks) it seems like it opens in the background, loads, and then gets moved to the foreground. So it could be that whatever is causing that regression is also causing this bug.

I'm not convinced this is a graphics-side bug, but if if you want to start digging into it from a graphics perspective the first place I would look is at the pause/resume methods on the compositor to see if the compositor is getting left in a paused state.

Comment 3

[Kris Taeleman (:ktaeleman)]

This also occurs without webrender, maybe just a bit less frequent pointing to a flow timing issue. Closing this bug to create a Fenix issu on github.

Github link: https://github.com/mozilla-mobile/fenix/issues/10250