When I set pref gfx.webrender.debug.force-picture-invalidation = true, I could reproduce the similar symptom easily. Then I wonder if it is related to Webrender picture cache.
Bug 1805347 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When I set pref gfx.webrender.debug.force-picture-invalidation = true, I could reproduce the similar symptom easily. Then I wonder if it is related to Webrender picture cache. "pref gfx.webrender.debug.force-picture-invalidation" was added by Bug 1678326.
When I set pref gfx.webrender.debug.force-picture-invalidation = true, I could reproduce the similar symptom easily. Then I wonder if it is related to Webrender picture cache. "pref gfx.webrender.debug.force-picture-invalidation" was added by Bug 1678326. With "pref gfx.webrender.debug.force-picture-invalidation = true", I got the following regression range. https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b422dd886e036907f35269f381f43785873c5296&tochange=69be3221f49a2acb92b734baf725e19bdf9a4fd9
When I set pref gfx.webrender.debug.force-picture-invalidation = true, I could reproduce the similar symptom easily. Then I wonder if it is related to Webrender picture cache. "pref gfx.webrender.debug.force-picture-invalidation" was added by Bug 1678326. With "pref gfx.webrender.debug.force-picture-invalidation = true", I got the following regression range. https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b422dd886e036907f35269f381f43785873c5296&tochange=69be3221f49a2acb92b734baf725e19bdf9a4fd9 I wonder if Bug 1692250 and Bug 1694305 might be related to the bug.