The immediate next step is mostly user outreach, to let affected users know that a permanent workaround exists. I have a draft of a FAQ; I'll need to finish that up, and also need to get in touch with :ahale to see what information is wanted from any users who experience bug 1638709 when they apply the workaround. Barring anyone chiming in to say the issue persists in 111b-plus-pref, that alone should be sufficient to reduce the bug's severity, and should be done before 111 sees release on Einstein's birthday. Following that, since we can now make the issue reproduce in Nightly, I'll be asking people (which probably mostly means :mhowell) to repro it with additional logging and some horrible workaround attempts that shouldn't make it into shipped code. This may be somewhat delayed, since I'm also handling at least one other P2 issue. Alternatively, :ahale may more precisely nail down the scope of bug 1638709 and entirely obviate the workaround in bug 1704954 for unaffected users. (The bug will still be present in the non-DirectComposition fallback code, but it won't be exposed as widely and can still be triggered intentionally for debugging.)
Bug 1763981 Comment 101 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The immediate next step is mostly user outreach, to let affected users know that a permanent workaround exists. I have a draft of a FAQ; I'll need to finish that up, and also need to get in touch with :ahale to see what information is wanted from any users who experience bug 1638709 when they apply the workaround. Barring anyone chiming in to say the issue persists in 111b-plus-pref, that alone should be sufficient to reduce the bug's severity, and should be done before 111 sees release on 2023-03-14. Following that, since we can now make the issue reproduce in Nightly, I'll be asking people (which probably mostly means :mhowell) to repro it with additional logging and some horrible workaround attempts that shouldn't make it into shipped code. This may be somewhat delayed, since I'm also handling at least one other P2 issue. Alternatively, :ahale may more precisely nail down the scope of bug 1638709 and entirely obviate the workaround in bug 1704954 for unaffected users. (The bug will still be present in the non-DirectComposition fallback code, but it won't be exposed as widely and can still be triggered intentionally for debugging.)