Additional data points - 1) Definitely tied in some way to a dual monitor setup, removing one screen from the device fixes the issue. 2) Checked in safe mode and with the OS compositor turned off, issue still reproduces. This implies the issue is not caused by NVidia's drivers or graphics pipeline code. 3) The setup is unique - dual monitors, one of which is 4K. Specific monitor orientation and layout settings, and mixed graphics refresh rates. My feeling right now is that this is not Graphics related. I'm also not convinced this is a widget bug, it might be related to something going wrong in Layout. ni'ing Frank, maybe the Layout Team can read this over and suggest additional steps we might take to try and debug. Note, David Parks is out for a bit, so he won't be able to work on this in the near future.
Bug 1609129 Comment 32 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Additional data points - 1) Definitely tied in some way to a dual monitor setup, removing one screen from the device fixes the issue. 2) Checked in safe mode and with the OS compositor turned off, issue still reproduces. This implies the issue is not caused by NVidia's drivers or graphics pipeline code. 3) The setup is unique - dual monitors, one of which is 4K. Specific monitor orientation and layout settings, and mixed graphics refresh rates. 4) scaling settings - 100% on the primary monitor, 175% on the secondary My feeling right now is that this is not Graphics related. I'm also not convinced this is a widget bug, it might be related to something going wrong in Layout. ni'ing Frank, maybe the Layout Team can read this over and suggest additional steps we might take to try and debug. Note, David Parks is out for a bit, so he won't be able to work on this in the near future.