Closed Bug 1148481 Opened 9 years ago Closed 9 years ago

Double Check DWM Composition Timing Information as Windows 10 gets close to release

Categories

(Core :: Graphics, defect, P2)

Product:
Core
Component:
Graphics
Platform:
x86_64
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mchang, Assigned: mchang)

References

Details

+++ This bug was initially created as a clone of Bug #1147953 +++

There are weird timing issues with Windows 10, Technical Preview 10041 and DwmFlush / DwmGetCompositionTimingInfo. The Vblank times vary wildly according to the timing info, and the dwm flush thread wakes up at very odd times as well. Windows 7, 8, and 8.1 all have very clean vblank timing information with these APIs.

In bug 1147953, we fell back to software vsync on Windows 10. Double check that the DWM apis are fixed on a close to release Windows 10 and delete the temporary fix.
We should reach out to Microsoft now to find out about what's going on here and whether we need to change or whether they will change.
The DwmGetCompositionTimingInfo makes sense on real hardware and may have been an issue due to VMWare. Resolving as WFM.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.