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
Maybe this is better for the Juliaup repo, but I'm not sure. Whenever I use MSession(), I always get this error:
julia>using MATLAB
julia>MSession()
Well, this is embarrassing.
Juliaup launcher had a problem and crashed. To help us diagnose the problem you can send us a crash report.
We have generated a report file at "C:\Users\User\AppData\Local\Temp\report-27153dcc-c4d1-4543-89fc-35f6ea8d76bd.toml". Submit an issue or email with the subject of "Juliaup launcher Crash Report" and include the report as an attachment.
- Homepage: https://github.com/JuliaLang/juliaup
We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.
Thank you kindly!
I'm trying to use R2023a. Is there any reason MSession() should be triggering this at all? Is anyone else able to reproduce this when using Julia installed with juliaup, or is it a MATLAB.jl issue?
julia>versioninfo()
Julia Version 1.9.1
Commit 147bdf428c (2023-06-0708:27 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU:32×13th Gen Intel(R) Core(TM) i9-13900K
WORD_SIZE:64
LIBM: libopenlibm
LLVM: libLLVM-14.0.6 (ORCJIT, goldmont)
Threads:24 on 32 virtual cores
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS =24
I can go post this on the juliaup if it doesn't seem like a MATLAB.jl issue.
The text was updated successfully, but these errors were encountered:
Maybe this is better for the Juliaup repo, but I'm not sure. Whenever I use
MSession()
, I always get this error:I'm trying to use R2023a. Is there any reason
MSession()
should be triggering this at all? Is anyone else able to reproduce this when using Julia installed with juliaup, or is it a MATLAB.jl issue?I can go post this on the juliaup if it doesn't seem like a MATLAB.jl issue.
The text was updated successfully, but these errors were encountered: