Skip to content
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

Empty Model Segfault (Julia v0.6) #1502

Closed
ccoffrin opened this issue Sep 28, 2018 · 4 comments
Closed

Empty Model Segfault (Julia v0.6) #1502

ccoffrin opened this issue Sep 28, 2018 · 4 comments

Comments

@ccoffrin
Copy link
Contributor

ccoffrin commented Sep 28, 2018

With Julia v0.6.4, JuMP master, SCS v0.4.0, and MOI v0.6.1. The following code results in a segfault for me,

using JuMP; using SCS

using MathOptInterface
const MOI = MathOptInterface
const MOIU = MOI.Utilities

m = Model()

MOIU.resetoptimizer!(m, SCS.Optimizer())
JuMP.optimize!(m)

My output is the following,

julia> JuMP.optimize!(m)
m and n must both be greater than 0; m = 0, n = 0
ERROR: Validation returned failure

signal (11): Segmentation fault: 11
while loading no file, in expression starting on line 0
scs_solve at /workspace/srcdir/scs-2.0.2/src/scs.c:838
Allocations: 7728582 (Pool: 7727033; Big: 1549); GC: 14
Segmentation fault: 11
@ccoffrin
Copy link
Contributor Author

ccoffrin commented Sep 29, 2018

Another example with similar behavior.

using JuMP; using SCS

using MathOptInterface
const MOI = MathOptInterface
const MOIU = MOI.Utilities

m = Model()

X = @variable(m, [1:3, 1:3], Symmetric)
y = @variable(m, [i in 1:3])

@constraint(m, X in PSDCone())

MOIU.resetoptimizer!(m, SCS.Optimizer())
JuMP.optimize!(m)

@blegat
Copy link
Member

blegat commented Sep 29, 2018

It was already the case with SCS with MathProgBase and JuMP v0.18, see e.g. 41a1a6d

@odow
Copy link
Member

odow commented Nov 7, 2018

Is this a JuMP issue or an SCS issue?

@blegat
Copy link
Member

blegat commented Nov 7, 2018

It is an SCS issue, it segfaults for empty model.
Closes in favor of jump-dev/SCS.jl#122

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants