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
I'm trying to write bindings to optimkit.jl; and for the most part they work. In essence I need matlab to call a julia function, which then calls small matlab functions (retraction, inner product, ...). However if I use it often enough, it sometimes segfaults. Because the failure is sporadic and at random, I would suspect the garbage collector sometimes cleaning things up that are still referenced?
I have attached some self-contained test code. setup_julia; test_mex; should work, but "for i =1:100; test_mex; end;" should crash somewhere down the line. I will also try to debug this further; now at least I get a stack trace. testmex.zip
Usually when I get errors on the julia side, I do get the stack trace in matlab, but further mex calls appear to lead to crashes. Not so here - I don't get a stack trace and the problem I give optimkit is extremely easy (3 x 3 hermitian matrix; smallest eigenvalue), an analogue implementation in julia does not error.
I'm trying to write bindings to optimkit.jl; and for the most part they work. In essence I need matlab to call a julia function, which then calls small matlab functions (retraction, inner product, ...). However if I use it often enough, it sometimes segfaults. Because the failure is sporadic and at random, I would suspect the garbage collector sometimes cleaning things up that are still referenced?
I have attached some self-contained test code. setup_julia; test_mex; should work, but "for i =1:100; test_mex; end;" should crash somewhere down the line. I will also try to debug this further; now at least I get a stack trace.
testmex.zip
stacktrace
Also, building mex.jl fails on 1.6, because it cannot find jl_options.
The text was updated successfully, but these errors were encountered: