-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ocaml5-issue] Windows failures on threadomain #203
Comments
This was previously observed on #179 - also on the Windows |
Following a discussion with @dra27, I wrote a dummy executable to trigger a segfault:
(-1073741819 is 0xc0000005, by the way). |
Which is indeed access violation / segfault 👍 |
Saw what looks like a deadlock and a 6 hour timeout on
|
Again experienced a likely deadlock and a 6 hour timeout on
|
Another likely deadlock and 6 hour timeout on
|
Another timeout on Windows
|
A Windows crash on Windows
|
#227 just saw 3 timeouts on Windows - 2 on |
Triggered again on Windows
|
Spotted again on Windows
|
Likely deadlock on Windows
|
Another Windows
|
TImeout again after 6h on Windows
|
Timeout after 6h on Windows
|
Same test failing on Windows
|
Crash observed on Windows
|
For the record, deadlock observed locally (mingw64 non-debug version, on powershell) with the following backtraces for the (only!) 4 threads:
|
Thanks! The fewer threads the better! 😅
I suspect Thread 4 is starting up a new pthread?
|
I think I understood from an analysis by @dra27 of another sets of backtraces that thread 4 is just
but maybe there’s a smart way to know where it is located? |
#11800 is supposedly about the debug runtime. This trace is in the normal (not debug) runtime. |
Thread 1 is trying to display:
As I don’t understand just how such a |
AFAIU, the debug runtime is the same runtime - just running with additional assertions enabled. |
This should be the
|
Timeout observed again on Windows 5.0.1+trunk
|
Another timeout on Windows 5.0.1+trunk:
|
A timeout in spawntree on Windows 5.0.0:
I suspect it might be the same cause, as many test runs let me think that the failures in |
Seeing a crash on Threadomain with Windows trunk:
|
Seen a segfault in that test in Windows bytecode version 5.0.0 + PR11846 😵💫
|
Timeout seen again on MingW bytecode 5.1 yesterday on merging #390 to
|
This triggered twice on the 0.3 branch on both Win bytecode 5.1 and trunk/5.2 5.1 https://github.com/ocaml-multicore/multicoretests/actions/runs/6481561494/job/17599327572
trunk/5.2 https://github.com/ocaml-multicore/multicoretests/actions/runs/6481561482/job/17599327577
|
The merge of 0.3 to
|
On the branch restoring support for MSVC (e55a77a30699ef15ce23bc2d53d9500d40b0aa8c), livelock with the bytecode version:
(with more than 3 hours between the last two lines) and with the native version:
(again with more than 3 hours between the last two lines). Also seen with seed 150874017. Logs: |
Closing this long-standing issue as this has been fixed in ocaml/ocaml#12882 🎉 |
We have also observed failures on Windows on the
threadomain
test combiningDomain
s andThread
s.Here is a fresh occurrence on
5.0.0~beta1
:https://github.com/jmid/multicoretests/actions/runs/3487203320/jobs/5834552533
This exits with a weird exit code
-1073741819
The text was updated successfully, but these errors were encountered: