http://bugs.winehq.org/show_bug.cgi?id=13687
--- Comment #28 from Alexandre Julliard julliard@winehq.org 2009-09-22 13:15:36 --- (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.