http://bugs.winehq.org/show_bug.cgi?id=59910 --- Comment #3 from Paul Gofman <pgofman@codeweavers.com> --- This test probably only fails on avx512 enabled machine (it does here, but not if avx512 is unsupported). The blamed commit added big chunk to xstate data when avx512 is supported, that how it is triggered the test failure. The process of unwinding / rethrowing goes down the stack and uses NtRaiseException to throw from inner catches. So the raised exception stack layout adds to stack usage and now that doesn't fit in. The issue is not present with WINE_ARCH=wow64, however the part which is different with wow64 which I spotted first is probably not quite right. If there is no xstate in the exception wow64's call_user_exception_dispatcher won't allocate space for xstate on stack. However on Windows NtRaiseException always ends up with xstate anyway, even if the supplied context doesn't have xstate, and probably in any case on Windows full xstate space ends up on stack always after raising exception. The actual related bug I found that i386 (non wow64) call_user_exception_dispatcher currently reserves the space for base context part twice (while always having xstate allocated looks right). Removing that double reservation looks enough for this test to fit in the default thread stack, I sent a patch: https://gitlab.winehq.org/wine/wine/-/merge_requests/11254 -- 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.