http://bugs.winehq.org/show_bug.cgi?id=59942 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #2 from Zeb Figura <z.figura12@gmail.com> --- (In reply to jesper from comment #0)
When sock_send decides to spill a remaining write from a short write, it calls itself (sock_send) recursively before calling async_set_result. The recursive call then schedules another write and waits on it. Since the outer sock_send (with the short write) never removed itself from the async queue, this new async call stalls behind it.
That doesn't seem right. The recursive send is FORCE_ASYNC, and it shouldn't be actually waited on. Are you observing it wait? (In reply to Ken Sharp from comment #1)
I assume you need a Mazda to test this? How does this communicate, USB, IP, etc.?
Please provide console logs. https://gitlab.winehq.org/wine/wine/-/wikis/Bugs
That's not useful in this case. -- 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.