Comment 91 for bug 205895

Revision history for this message
In , Alexandre Julliard (julliard) wrote :

(In reply to comment #27)
> Therefore, this change does not explain the original problem AFAIK. Certainly,
> the original problem was not reproduced in this test.
>
> I do not believe this shows the 100% CPU problem is in native crypt32.

It is very much in crypt32. It registers a wait with 0 timeout which causes an infinite loop. If you don't believe me get a relay trace and check for yourself.