[Bug 50448] Recent changes to ntdll-NtAlertThreadByThreadId causes that threads in some applications might look up causing periodical lookups

WineHQ Bugzilla wine-bugs at winehq.org
Wed Jan 6 04:08:46 CST 2021


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

Paul Gofman <pgofman at codeweavers.com> changed:

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

--- Comment #8 from Paul Gofman <pgofman at codeweavers.com> ---
(In reply to Zebediah Figura from comment #5)

> 
> It must be depending on the thread never grabbing the loader lock, or
> releasing the loader lock by the time the wait returns, both of which seem
> more than a little suspicious.
> 

Windows (modern) loader implementation is known to take loader lock in much
less number of cases than Wine currently does (see my patches [1] with an
attempt to move that way which I made in regards to the other random lock up I
came through without relation to the patchset concerned here). Do you know
which functions lead to taking loader lock here? E. g., GetProcAddress() and
GetModuleHandle() take the loader lock now in Wine but not on Windows. However,
there are much more functions with excessive locking than are currently
concerned by the linked patchset.


1. https://www.winehq.org/pipermail/wine-devel/2020-November/177695.html

-- 
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.



More information about the wine-bugs mailing list