You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
whenever I solve an infeasible LP problem. Actually, the solution appears to complete correctly, but the crash occurs when I try to return from my function. I tried lots of things, like deleting my model with
del scip
but that just triggers the crash anyway. So it must be caused by some internal memory mismanagement within pyscipopt.
The exact same code works perfectly when the LP is feasible.
I just want to determine feasibility, That is correctly being determined, but I can't return from my function. i should have said that I am using vtype='B'.
Alright. Maybe the issue is the same that PR #1161 is fixing, of variables and constraints not being properly freed upon model deletion. Assuming this is indeed the fix, it will only be properly available via PyPi once we add a new release, only after SCIP has a new minor release (shouldn't take more than a month). So, unfortunately, you would have to compile PySCIPOpt yourself.
Local compilation of PySCIPOpt is done with
git clone https://github.com/scipopt/PySCIPOpt.git
cd PySCIPOpt
git checkout fix-freeTransform-segfault
export SCIPOPTDIR=your/SCIP/binary/directory # if not installed globally. if needed, you can download a precompiled packaged from https://www.scipopt.org/index.php#download
pip install .
Also, if feasibility is only what you're after, it can be more performant to use the following:
Trying to install scipoptsuite_10.0.0-1+trixie_amd64.deb on my Ubuntu 24 system, I get: scipoptsuite : Depends: libopenmpi40 (>= 5.0.7) but it is not installable
Thanks, that works and then the the pip install works.
But the signal 11 problem is not fixed. It happens as soon as I try to do any manipulations on the model, or try to return from my function. Making the model global, which should mean that it is not deleted upon function return, still doesn't fix it.
I made a small minimal example - but it did not show the problem. I probably have to make a bigger one.
Activity
Joao-Dionisio commentedon Jan 21, 2026
Hey @keithbriggs ! Can you please share a minimal reproducible example?
keithbriggs commentedon Jan 21, 2026
Not easy - it's in the middle of a large code.
Joao-Dionisio commentedon Jan 21, 2026
Can you then please tell me what you're trying to do with the LP you get, and potentially also share the LP?
keithbriggs commentedon Jan 21, 2026
I just want to determine feasibility, That is correctly being determined, but I can't return from my function. i should have said that I am using vtype='B'.
Joao-Dionisio commentedon Jan 21, 2026
Alright. Maybe the issue is the same that PR #1161 is fixing, of variables and constraints not being properly freed upon model deletion. Assuming this is indeed the fix, it will only be properly available via PyPi once we add a new release, only after SCIP has a new minor release (shouldn't take more than a month). So, unfortunately, you would have to compile PySCIPOpt yourself.
Local compilation of PySCIPOpt is done with
Also, if feasibility is only what you're after, it can be more performant to use the following:
Please let me know if this fixes things, or if you're having problems with the compilation.
keithbriggs commentedon Jan 21, 2026
I was already doing SCIP_PARAMEMPHASIS.FEASIBILITY. I will try the local compile.
keithbriggs commentedon Jan 21, 2026
Trying to install scipoptsuite_10.0.0-1+trixie_amd64.deb on my Ubuntu 24 system, I get:
scipoptsuite : Depends: libopenmpi40 (>= 5.0.7) but it is not installableJoao-Dionisio commentedon Jan 21, 2026
Strange... Maybe the easiest is to just do
keithbriggs commentedon Jan 21, 2026
Thanks, that works and then the the pip install works.
But the signal 11 problem is not fixed. It happens as soon as I try to do any manipulations on the model, or try to return from my function. Making the model global, which should mean that it is not deleted upon function return, still doesn't fix it.
I made a small minimal example - but it did not show the problem. I probably have to make a bigger one.
keithbriggs commentedon Jan 21, 2026
Ok, I found that the bug is triggered by calling
getSolTime(sol)in the infeasible case. When I take out this call, everything works.Joao-Dionisio commentedon Jan 21, 2026
Ah that makes sense, but it should still be fixed on our end. Thank you for the issue! I'll create a patch soon.
Also, if you don't mind, I enjoyed browsing a bit through your website, quite interesting stuff :)