# Problem with visual studio code and LinearAlgebra

**URL:** <https://discourse.julialang.org/t/problem-with-visual-studio-code-and-linearalgebra/98100>\
**Category:** New to Julia\
**Created:** [April 29, 2023, 8:25pm UTC](https://discourse.julialang.org/t/problem-with-visual-studio-code-and-linearalgebra/98100 "2023-04-29T20:25:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marco\_menarini](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marco_menarini/32/46117_2.png) [@marco\_menarini](https://discourse.julialang.org/u/marco_menarini)\
**Post date:** [April 29, 2023, 8:25pm UTC](https://discourse.julialang.org/t/problem-with-visual-studio-code-and-linearalgebra/98100/1 "2023-04-29T20:25:25Z")

</div>

I have a problem that is difficult to diagnose. I generated a sparse matrix and a vector, all the elements are allocated, if I run the function step by step in VS Code everything seems to work fine, but when I just run Julia crashes leaving behind the message in the image (I had to screenshoot it because it disappears as soon as Julia crashes)

The operation is a simple

A\b between a Sparse ComplexF64 non singular tridiagonal matrix A and a nonzero complex vector b

 ![image](https://global.discourse-cdn.com/julialang/original/3X/0/4/042f593e2c040021063d4e7173d04118a3733d58.png)

---

<div class="post-metadata">

**Author:** ![marco\_menarini](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marco_menarini/32/46117_2.png) [@marco\_menarini](https://discourse.julialang.org/u/marco_menarini)\
**Post date:** [April 29, 2023, 8:37pm UTC](https://discourse.julialang.org/t/problem-with-visual-studio-code-and-linearalgebra/98100/2 "2023-04-29T20:37:19Z")

</div>

It seems to be a problem with the SuiteSparse, but I don’t understand it

in expression starting at none:1  
\_\_fu1133\_SuiteSparse\_config at C:\Users\menar\AppData\Local\Programs\Julia-1.8.1\bin\libumfpack.DLL (unknown line)  
.text at C:\Users\menar\AppData\Local\Programs\Julia-1.8.1\bin\libumfpack.DLL (unknown line)  
.text at C:\Users\menar\AppData\Local\Programs\Julia-1.8.1\bin\libumfpack.DLL (unknown line)  
umfpack\_zl\_numeric at C:\Users\menar\AppData\Local\Programs\Julia-1.8.1\bin\libumfpack.DLL (unknown line)  
umfpack\_zl\_numeric at C:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.8\SuiteSparse\lib\x86\_64-w64-mingw32.jl:1760  
#umfpack\_numeric!#15 at C:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.8\SuiteSparse\src\umfpack.jl:398  
umfpack\_numeric! at C:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.8\SuiteSparse\src\umfpack.jl:394 [inlined]  
#lu#1 at C:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.8\SuiteSparse\src\umfpack.jl:202  
lu at C:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.8\SuiteSparse\src\umfpack.jl:195 [inlined]  
\ at C:\buildbot\worker\package\_win64\build\usr\share\julia\stdlib\v1.8\SparseArrays\src\linalg.jl:1564  
unknown function (ip: 000000014f313a04)  
jl\_apply at /cygdrive/c/buildbot/worker/package\_win64/build/src\julia.h:1838 [inlined]  
do\_call at /cygdrive/c/buildbot/worker/package\_win64/build/src\interpreter.c:126  
eval\_value at /cygdrive/c/buildbot/worker/package\_win64/build/src\interpreter.c:215  
eval\_body at /cygdrive/c/buildbot/worker/package\_win64/build/src\interpreter.c:467  
jl\_interpret\_toplevel\_thunk at /cygdrive/c/buildbot/worker/package\_win64/build/src\interpreter.c:750  
jl\_toplevel\_eval\_flex at /cygdrive/c/buildbot/worker/package\_win64/build/src\toplevel.c:906  
ijl\_toplevel\_eval at /cygdrive/c/buildbot/worker/package\_win64/build/src\toplevel.c:915 [inlined]  
ijl\_toplevel\_eval\_in at /cygdrive/c/buildbot/worker/package\_win64/build/src\toplevel.c:965  
eval at .\boot.jl:368 [inlined]  
eval\_code at c:\Users\menar.vscode\extensions\julialang.language-julia-1.45.1\scripts\packages\JuliaInterpreter\src\utils.jl:685  
eval\_code at c:\Users\menar.vscode\extensions\julialang.language-julia-1.45.1\scripts\packages\JuliaInterpreter\src\utils.jl:658  
evaluate\_request at c:\Users\menar.vscode\extensions\julialang.language-julia-1.45.1\scripts\packages\DebugAdapter\src\debugger\_requests.jl:1006  
#137 at c:\Users\menar.vscode\extensions\julialang.language-julia-1.45.1\scripts\packages\DebugAdapter\src\packagedef.jl:64  
unknown function (ip: 000000014f2ed4ff)  
dispatch\_msg at c:\Users\menar.vscode\extensions\julialang.language-julia-1.45.1\scripts\packages\JSONRPC\src\typed.jl:67  
macro expansion at c:\Users\menar.vscode\extensions\julialang.language-julia-1.45.1\scripts\packages\DebugAdapter\src\packagedef.jl:76 [inlined]  
#146 at .\task.jl:484  
unknown function (ip: 000000005f51d7f3)  
jl\_apply at /cygdrive/c/buildbot/worker/package\_win64/build/src\julia.h:1838 [inlined]  
start\_task at /cygdrive/c/buildbot/worker/package\_win64/build/src\task.c:931  
Allocations: 7417916270 (Pool: 7417843066; Big: 73204); GC: 173

---

<div class="post-metadata">

**Author:** ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)\
**Post date:** [April 29, 2023, 9:13pm UTC](https://discourse.julialang.org/t/problem-with-visual-studio-code-and-linearalgebra/98100/3 "2023-04-29T21:13:10Z")

</div>

Could it be an “out of memory” error?

---

<div class="post-metadata">

**Author:** ![marco\_menarini](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marco_menarini/32/46117_2.png) [@marco\_menarini](https://discourse.julialang.org/u/marco_menarini)\
**Post date:** [April 29, 2023, 9:38pm UTC](https://discourse.julialang.org/t/problem-with-visual-studio-code-and-linearalgebra/98100/4 "2023-04-29T21:38:29Z")

</div>

I don’t think so… usually it gives me out of memory as an error, plus the matrices are relatively small (I made a domain decomposition implementation).

The other thing that is frustrating is that if the code crash there it’s done but otherwise it works like a charm and I do not understant how or why. Everything is deterministic up to that point in the code