[Development] Windows Timer Resolution: The Great Rule Change

[Philippe]

> > Thiago Macieira <thiago.macieira at intel.com> wrote:
> If nothing is signaled, why are they waking up at all?

Let me rephrase otherwise:
if one calls WaitForSingleObject or WaitForMultipleObjects
with a timeout of 1 millisecond, then these functions
won't return before 15 milliseconds (provided the events don't get
signaled during that period).

Philippe

On Thu, 8 Oct 2020 14:02:49 -0700
Thiago Macieira <thiago.macieira at intel.com> wrote:

> On Thursday, 8 October 2020 01:43:38 PDT Philippe wrote:
> > On Wed, 7 Oct 2020 17:34:43 -0700
> > 
> > Thiago Macieira <thiago.macieira at intel.com> wrote:
> > > Now, the question is how WaitFor{SingleObject,MultipleObjects} are
> > > affected. Does this mean that asking for a timeout of 2 milliseconds
> > > could result in being 13 seconds too late?
> > 
> > I just did a test, and yes, both WaitForSingleObject and
> > WaitForMultipleObjects wait at least 15 milliseconds when the events are not
> > signaled :(
> 
> If nothing is signaled, why are they waking up at all?
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel DPG Cloud Engineering
> 
> 
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> https://lists.qt-project.org/listinfo/development