http://bugs.winehq.org/show_bug.cgi?id=11674
--- Comment #227 from sworddragon2@aol.com 2012-09-19 13:21:33 CDT ---
multitreads under wine have one main problem - realization of WaitMultipleObject is realized through wineserver on windows it is realized in a kernel and while it do not realize more correctly - through a kernel or ~ in wine - that actively working multithread appendices and will miraculously brake
Can you explain what WaitMultipleObject(s) is doing exactly and why it has a performance impact because the wineserver realizes it? How could Wine solve this performance problem?
Currently Windows applications can create threads under Linux and now with Wine 1.5.13 they can even get the correct processor informations. Shouldn't this ticket be renamed to a more generic one that points to this problem (like "Multithreading not fully supported")?