-
Notifications
You must be signed in to change notification settings - Fork 22
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
Minzinc crash #147
Comments
Removing some of the constrains, the model runs without crashing. The problem is that with that message, it's impossible to debug it. Is there any log file to look at? |
Same problem. Minizinc 2.5.5. |
In general this error message indicates that MiniZinc has crashed. MiniZnc 2.6.0 features better error reporting for this, so it would be great if you could try out this version. @alexeytref If your issue is still present in 2.6.0, could you open a new issue on the https://github.com/MiniZinc/libminizinc repository describing the problem (and if possible include a code example which demonstrates the issue)? It's likely not the same as the issue with CPLEX. |
@cyderize |
Hi,
Running latest version v2.5.5 but as well with v2.5.4. I run a model and sometimes works and sometimes crashes with window message "unknown error while executing minizinc: crashed" and on the ouput "Process finished with non-zero exit code -1073741819".
I use CPLEX for the solver (v20.1 and v12.9) both with the same result.
If I run v2.5.3 I got the following error:
C:\Program Files\MiniZinc\share\minizinc/linear//fzn_lex_lesseq_int.mzn:14.8-20:
MiniZinc: type error: undefined identifier `MZN__Orbisack'
Process finished with non-zero exit code 1
I used to run same model with cplex 12.9 and Minizinc ide v2.3.2 and it worked perfectly. I tried to re-installed both previous versions of cplex and minizinc but I cannot get minizinc to load the cplex solver "MiniZinc: internal error: cannot load cplex dll `cplex12100.dll'. ¿Any idea how to update the configuration file for minizinc of cplex solver?
Any idea how to proceed?
The text was updated successfully, but these errors were encountered: