-
Notifications
You must be signed in to change notification settings - Fork 110
Closed
Description
Another point. I am using XGBoost.jl v2.2.0, under Windows 11.
It works fine with Julia 1.8.3:
julia> versioninfo()
Julia Version 1.8.3
Commit 0434deb161 (2022-11-14 20:14 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 16 × Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-13.0.1 (ORCJIT, skylake)
Threads: 8 on 16 virtual cores
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS = 8
But when I uses Julia 1.8.4:
julia> versioninfo()
Julia Version 1.8.4
Commit 00177ebc4f (2022-12-23 21:32 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: 16 × Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-13.0.1 (ORCJIT, skylake)
Threads: 8 on 16 virtual cores
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS = 8
running any function of XGBoost.jl kills my Julia session, for instance after doing:
using XGBoost
(X, y) = (randn(100,4), randn(100))
then the command below;
bst = xgboost((X, y))
kills the process and closes directly Julia without any printed error in the terminal.
I created a thread at Discourse, but got no answer. I have the same problem with LIBSVM.jl (that also uses an external library, as does XGBoost; this may be linked). I created an issue there but the problem was not solved.
Did somebody observe the same problem and know what is happening?
Metadata
Metadata
Assignees
Labels
No labels