http://bugs.winehq.org/show_bug.cgi?id=33235
Daniel Jelinski djelinski1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |djelinski1@gmail.com
--- Comment #12 from Daniel Jelinski djelinski1@gmail.com 2013-03-19 08:18:55 CDT --- (In reply to comment #11)
If you mean that PeekMessage doesn't yield cpu and therefore it shouldn't be used to write message loops, then this is not correct. Message loops that use PeekMessage are equivalent in behaviour to the ones that use GetMessage.
PeekMessage returns immediately, and message loop based on PeekMessage without WaitMessage will consume all CPU cycles it can get. See also bug 30736, which is caused exactly by this.