On Thu May 15 16:00:35 2025 +0000, Bernhard Übelacker wrote:
Thanks for your patience, I rearranged the test to put the intermediate between both ctrl-c tests. Unfortunately I can't now tell which process 0x61c was. Trying to continue to test.
I did some more tests and found without current git without this patch I can quite reliable reproduce the issue, this are some points which I think are important: - happens with both, old- and new-wow64 - load some stress on the cpu: `stress --cpu 16` - `WINEDLLOVERRIDES=winemenubuilder.exe=n WINEDEBUG=+pid WINETEST_DEBUG=10 wine programs/winetest/i386-windows/winetest.exe -o - -J - timeout.exe`
Following example may be interesting, because the last timeout.exe execution start is logged while timeout.exe_test.exe seems already finished: ``` Test output: timeout.exe:timeout start programs/timeout/tests/timeout.c 0134:0138:err:environ:init_peb starting L"C:\users\bernhard\AppData\Local\Temp\wct2b8a.tmp\timeout.exe_test.exe" in experimental wow64 mode 0144:0148:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 014c:0150:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 0154:0158:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 015c:0160:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 0164:0168:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 016c:0170:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 0174:0178:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 017c:0180:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 0184:0188:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 018c:0190:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode 018c:0194:fixme:console:default_ctrl_handler Terminating process 18c on event 0 0134:0198:fixme:console:default_ctrl_handler Terminating process 134 on event 0 timeout.c:61:2.141 Test succeeded timeout.c:65:3.482 Test succeeded timeout.c:69:4.699 Test succeeded timeout.c:135:7.510 Test succeeded timeout.exe:timeout:0134 done (-1073741510) in 7s 141B 019c:01a0:err:environ:init_peb starting L"C:\windows\syswow64\timeout.exe" in experimental wow64 mode ```
Without this MR's patch and the stressed cpu the issue shows up in around 5 of 10 attempts.
With this MR's patch in the same environment 10 of 10 runs did succeed.