-
Notifications
You must be signed in to change notification settings - Fork 58
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
Optimizing multiple models with Ipopt and JuMP in parallel results in crashes #257
Comments
I got another, more descriptive error message:
|
MUMPS is known to be not thread safe. See e.g. the discussion in this issue: #190
|
Oh, that's a pity... Will try to use Anyway, a straight up segmentation fault is highly confusing. Maybe it's possible to detect that the code is run in "multithreaded mode" and warn the user. |
I agree facing segfault in Julia is always puzzling ... |
Since Julia positions itself as a language with simple parallelism, I attempted to run multiple optimisations in parallel. However, I got a double-free error.
This Julia code (
bug.jl
) attempts to create and optimise one model per thread:Error messages
First run:
Second run (it says
[SIGABRT]
because it continues from the last prompt above):Third run:
Sometimes it simply says
fish: 'julia --threads=4 --project=bug…' terminated by signal SIGSEGV (Address boundary error)
, without any additional errors.Looks like
mumps
is to blame. Another error that I now can't reproduce was complaining aboutdmumps_load.F
(that GitHub project seems kinda dead...).I have 3.5 GB of free memory, the
julia
process maxed out at 492 MB (!!) and crashed.Versions
Project.toml
:Installed JuMP and Ipopt like this:
Regular non-development versions result in the same errors.
It would've been nice not to crash, I guess?
One of the errors says:
Maybe it's possible to catch this and propagate this error to Julia code?
BTW, everything works fine when I remove
Threads.@threads
.The text was updated successfully, but these errors were encountered: