[Bug 48052] kernel32:debugger - Wine randomly fails to get the thread context

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48052

Jacek Caban <jacek at codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jacek at codeweavers.com

--- Comment #1 from Jacek Caban <jacek at codeweavers.com> ---
This race is not related to the race I was working on when writing those tests.
This seems related to a known limitation (race?) in Wine:
https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ntdll/thread.c#l819

Due to the way get_thread_context works, it may timeout in Wine and
STATUS_ACCESS_DENIED is returned in such case. This cannot happen on Windows. I
guess we could try to limit thread number based on CPU count to avoid CPU load
(we currently run 20 threads, each one is running a loop).

While looking at that I noticed that all TestBot VMs run on a single core. Is
there a reason for that? It does not really reflect how things are ran on real
hardware those days...

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.