Bug 1576166 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug!

As I type, time occasionally skips back a frame to show an earlier version of my text.

The most distressing part: firefox is using my NVIDIA Quadro M2200, and not the Intel Graphics!

about:support attached with hardware/software details
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug!

The most distressing part: firefox is using my NVIDIA Quadro M2200, and not the Intel Graphics!

about:support attached with hardware/software details

STR:
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug!

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with hardware/software details

STR: 

* Have firefox be a non-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). Interestingly if I have my window maximized *and* the taskbar hidden, the bug doesn't reproduce!
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug!

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with hardware/software details

Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"

STR: 

* Have firefox be a non-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). Interestingly if I have my window maximized *and* the taskbar hidden, the bug doesn't reproduce!
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with hardware/software details

Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"

STR: 

* Have firefox be a non-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). Interestingly if I have my window maximized *and* the taskbar hidden, the bug doesn't reproduce!
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with hardware/software details

Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"

STR: 

* Have firefox be a non-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). Interestingly if I have my window maximized *and* the taskbar hidden (so firefox is covering every pixel on my laptop's monitor), the bug doesn't reproduce!
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with hardware/software details

Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"

STR: 

* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). Interestingly if I have my window maximized *and* the taskbar hidden (so firefox is covering every pixel on my laptop's monitor), the bug doesn't reproduce!
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). 

---------------------

Notes from testing what causes the issue:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200 
* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment). 

---------------------

Notes About System Configuration:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200
* NVIDIA Control Panel: Overridden to use NVIDIA for Firefox

-----------------------

Notes from testing what causes the issue:

* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
* If I go into the NVIDIA panel and force firefox to use Integrated Graphics, the bug also goes away
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar (small fast bursts)

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment; or if hitting backspace, making them reappear).

---------------------

Notes About System Configuration:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200
* NVIDIA Control Panel: Overridden to use NVIDIA for Firefox

-----------------------

Notes from testing what causes the issue:

* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
* If I go into the NVIDIA panel and force firefox to use Integrated Graphics, the issue goes away
* Setting the native display to have "scale: 100%" does not fix the issue
* Setting the secondary display to have "scale: portrait" does not cause it to start having the issue
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar (small fast bursts)

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment; or if hitting backspace, making them reappear).

---------------------

Notes About System Configuration:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200
* NVIDIA Control Panel: Overridden to use NVIDIA for Firefox

-----------------------

Notes from testing what causes the issue:

* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
* If I go into the NVIDIA panel and force firefox to use Integrated Graphics, the issue goes away
* Setting the native display to have "scale: 100%" does not fix the issue
* Setting the secondary display to be in landscape does not cause it to start having the issue
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar (small fast bursts)

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment; or if hitting backspace, making them reappear).

---------------------

Notes About System Configuration:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200
* NVIDIA Control Panel: Overridden to use NVIDIA for Firefox

-----------------------

Notes from testing what causes the issue:

* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
* If I go into the NVIDIA panel and force firefox to use Integrated Graphics, the issue goes away. Moving the intel-controlled window to the NVIDIA-controleld display does not cause the issue.
* Setting the native display to have "scale: 100%" does not fix the issue
* Setting the secondary display to be in landscape does not cause it to start having the issue
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar (small fast bursts)

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment; or if hitting backspace, making them reappear).

---------------------

Notes About System Configuration:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200
* NVIDIA Control Panel: Overridden to use NVIDIA for Firefox

-----------------------

Notes from testing what causes the issue:

* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
* If I go into the NVIDIA panel and force firefox to use Integrated Graphics, the issue goes away. Moving the intel-controlled window to the NVIDIA-controleld display does not cause the issue.
* Setting the native display to have "scale: 100%" does not fix the issue
* Setting the secondary display to be in landscape does not cause it to start having the issue
* Disabling the Intel GPU at the OS level (causing windows to use some sort of software fallback), causes the issue to go away (unsurprising).
Came into the office this morning, booted up my fully updated windows 10 laptop, got prompted for an OS update, and installed it. I now have the time-travelling compositor bug! That is, the same issue described in Bug 1556634 and Bug 1525084.

The most distressing part: **firefox is using my NVIDIA Quadro M2200**, and not the Intel Graphics!

I also see it with **and without** webrender!

about:support attached with some hardware/software details, more details in notes section.

--------------------

STR: 
* Have firefox be a **non**-fullscreen window
* Type quickly and erratically in the awesome bar (small fast bursts)

result: browser occasionally shows an old frame, making text occasionally "jump back" (visually erasing some characters for a moment; or if hitting backspace, making them reappear).

---------------------

Notes About System Configuration:

* Windows Version: "10.0.18362 (build 18362)" AKA "OS build 18362.295" AKA "Windows 10 Pro Version 1903"
* Displays: 
  * Builtin Lenovo P51 Laptop Display: 
    * 3849 x 2160 @ 60 Hz
    * scale 250%
    * "connected to" Intel(R) HD Graphics P630 (!!!!)
  * HDMI-connected DELL U2410: 
    * 1920 x 1200 @ 60 Hz, rotated in portrait
    * scale 100%
    * "connected to" NVIDIA Quadro M2200
* NVIDIA Control Panel: Overridden to use NVIDIA for Firefox

-----------------------

Notes from testing what causes the issue:

* If I move the window to the DELL U2410, the issue goes away. If I move the same window back to my laptop display, the issue resumes!
* On my native laptop display, if the window is maximized *and* the taskbar is hidden (so firefox is covering every pixel), the issue goes away
* If I go into the NVIDIA panel and force firefox to use Integrated Graphics, the issue goes away. Moving the intel-controlled window to the NVIDIA-controleld display does not cause the issue.
* Setting the native display to have "scale: 100%" does not fix the issue
* Setting the secondary display to be in landscape does not cause it to start having the issue
* Disabling the Intel GPU at the OS level (causing windows to use some sort of software fallback), causes the issue to go away (unsurprising).
* Disabling the secondary display does not fix the issue.

Back to Bug 1576166 Comment 0