https://bugs.winehq.org/show_bug.cgi?id=45546
--- Comment #15 from Anton Romanov theli.ua@gmail.com --- (In reply to Anastasius Focht from comment #13)
(timing) analysis of the MTGA updater/Mono-Runtime on your own, backing whatever alternative conclusion you come to. Waiting for it ...
your own traces show that multiple threads are pending on get_thread_context. get_thread_context is a wineserver call and wineserver is single threaded. That means that they all get queued up and whoever is a bit later to the party has its latency increased.
(In reply to Zebediah Figura from comment #14)
I think Anton's point is it's not clear why the function should be *expected* possibly to never return; i.e. why was that contingency added in the first place?
Yup, why was it implemented in a such a way that it times out and returns ACCESS DENIED instead of just waiting indefinitely.