-
Notifications
You must be signed in to change notification settings - Fork 114
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
Multithreaded simulations freeze sometimes #683
Comments
I have the same issue intermittently (most recently related to JuliaLinearAlgebra/Octavian.jl#103). I've also noticed this with Polyester.reset_workers!()
ThreadingUtilities.reinitialize_tasks!() |
How do I do a reset in a frozen simulation? |
If the simulation hangs, then I have to interrupt (ctrl or command-c). Sometimes the simulation completely freezes, in which case restarting the REPL is the only way I've found. |
After interrupting, I can just start the simulation again (not sure if it then hangs somewhere else). |
Yeah, the Octavian issue is specific to using Polyester, Octavian, and VSCode. I've had |
I've found that the hanging is sometimes related to error handling, e.g., complex square root argument errors. |
Yes! This seems to be exactly what's happening here. My simulations only freeze at the exact same time step where |
Perhaps we should raise an issue in Polyester.jl, esp if we could put a MWE together? |
Alright, I found the problem and created two issues. See JuliaSIMD/Polyester.jl#30 and JuliaSIMD/Polyester.jl#31. |
Does this still happen for you? Or is it resolved (maybe by #708) on |
It now shows the error instead of freezing, but it still runs only serially after that for the session. |
Thanks for testing it again. |
I take it back, it's still freezing sometimes. |
I've had multithreaded simulations freeze multiple times lately. Interrupting the simulation works immediately, though.
The interruption error always looks like this:
It's always the
@threaded
block of the used volume integral.Has this happened to anyone else before? Is there a way to debug stuff like this?
The text was updated successfully, but these errors were encountered: