4 | | This only happens in GTK4 because the |
5 | | views opened in new tabs stay |
6 | | unrealized until they are shown. With |
7 | | the DMA-BUF rendered enabled we keep |
8 | | processing frames while the view is |
9 | | unrealized, just pretending they have |
10 | | been rendered on screen. This causes |
11 | | the page to be throttled, because it's |
12 | | visually idle, which changes the |
13 | | preferred frame rate from 60 to 30. |
14 | | This new condition makes |
15 | | DisplayUpdate::relevantForUpdateFrequen |
16 | | cy() always return false, leaving the |
17 | | last frame scheduled forever, because |
18 | | DisplayRefreshMonitorClient::fireDispla |
19 | | yRefreshIfNeeded() doesn't update the |
| 4 | This only happens in GTK4 because the views opened in new tabs stay |
| 5 | unrealized until they are shown. With the DMA-BUF rendered enabled we keep |
| 6 | processing frames while the view is unrealized, just pretending they have |
| 7 | been rendered on screen. This causes the page to be throttled, because it's |
| 8 | visually idle, which changes the preferred frame rate from 60 to 30. |
| 9 | This new condition makes DisplayUpdate::relevantForUpdateFrequen |
| 10 | cy() always return false, leaving the last frame scheduled forever, because |
| 11 | DisplayRefreshMonitorClient::fireDisplayRefreshIfNeeded() doesn't update the |