JuliaPro 1.01.1 crashes on older PC running Windows 10 64-bit

Tooling
1

Hi,

I’ve installed and run JuliaPro 1.01.1 on several PCs running Windows 10 64-bit without a problem. However, this older machine seems to have crashed Julia.

Not sure if it’s related, but the machine’s CPU is a bit old: Intel Core i7 X 980. It used to have problem with C++ binary built in Visual C++ with “Enable Enhanced Instruction Set” turned on because the CPU lacks AVX support. That’s the only oddity I can remember with this machine.

JuliaPro was installed with Administrator privilege. The OS is Windows 10 Enterprise 64-bit version 10.0.15063. 8GB RAM.

Below’s the crash message. Can someone help or give me some direction to look? Thanks!

julia
fatal: error thrown and no exception handler available.
InitError(mod=:MbedTLS, error=MethodError(f=typeof(Base.Filesystem.joinpath)(), args=(nothing, “…”, “…”, “deps”, “usr”, “lib”), world=0x000000000000673a))
rec_backtrace at /home/Administrator/buildbot/worker/package_win64/build/src\stackwalk.c:94
record_backtrace at /home/Administrator/buildbot/worker/package_win64/build/src\task.c:246
jl_throw at /home/Administrator/buildbot/worker/package_win64/build/src\task.c:577
jl_method_error_bare at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:1616
jl_method_error at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:1634
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2161
init at C:\Users\julia\AppData\Local\Julia-1.0.1\share\julia\stdlib\v1.0\MbedTLS\src\MbedTLS.jl:61
jfptr___init___21367 at C:\JuliaPro-1.0.1.1\Julia-1.0.1\lib\julia\sys.dll (unknown line)
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2184
jl_apply at /home/Administrator/buildbot/worker/package_win64/build/src\julia.h:1537 [inlined]
jl_module_run_initializer at /home/Administrator/buildbot/worker/package_win64/build/src\toplevel.c:90
_julia_init at /home/Administrator/buildbot/worker/package_win64/build/src/home/Administrator/buildbot/worker/package_win64/build/src\init.c:813
julia_init__threading at /home/Administrator/buildbot/worker/package_win64/build/src\task.c:302
wmain at /home/Administrator/buildbot/worker/package_win64/build/ui\repl.c:227
__tmainCRTStartup at /usr/src/debug/mingw64-x86_64-runtime-5.0.3-1/crt\crtexe.c:329
mainCRTStartup at /usr/src/debug/mingw64-x86_64-runtime-5.0.3-1/crt\crtexe.c:212
BaseThreadInitThunk at C:\WINDOWS\System32\KERNEL32.DLL (unknown line)
RtlUserThreadStart at C:\WINDOWS\SYSTEM32\ntdll.dll (unknown line)

Update: Verified that only JuliaPro installation has this problem; Julia 1.01.1 can be started properly on the same machine.

2

Problem solved, though I still don’t know why.

Since JuliaPro 1.01.1 was crashing, I tried the standard Julia 1.01.1. I could run julia.exe without crashing, but when I tried to add any package, “ERROR: no active project” would show up and operation would fail.

I searched this error message online and found this post:

Since JULIA_LOAD_PATH was mentioned in this post, and on this machine I had JULIA_LOAD_PATH pointing to 2 paths where I created my own modules, I tried removing the JULIA_LOAD_PATH environmental variable.

After that, magically the Julia package adding started working. I then tried re-installing JuliaPro 1.01.1, and it also worked!

I still don’t know why. On another Windows 10 64-bit machine I also had JULIA_LOAD_PATH pointing to similar paths, but that machine had no problem with JuliaPro.

Anyway, I’m happy it’s working now.

3

You’re probably right, except the cause being AVX. I doubt it’s used in crypto, but CPUs now also have some instructions for that, but not older, and I guess not that one.

It seems this line 61 is the problem:

function __init__()
__ctr_drbg__init__()

or what it call here (possibly it’s inlined):

I would have expected " signal (4): Illegal instruction" like in (but possibly such appears only on Linux and not on Windows)?: Error starting Julia: invalid instruction 0x62 · Issue #29652 · JuliaLang/julia · GitHub

4

Hi, I am also having the same MbedTLS initError but when trying to build CUDAdrv. This is on a i5-7600K CPU with Ubuntu. I tried Julia 1.0.1 and JuliaPro 1.0.1.1. Is my error related? I added a JULIA_LOAD_PATH and it still failed.

julia> Pkg.build("CUDAdrv")
  Building CUDAdrv → `/home/julia/JuliaPro-1.0.1.1/JuliaPro/pkgs-1.0.1.1/packages/CUDAdrv/9tzHS/deps/build.log`
┌ Error: Error building `CUDAdrv`:
│ fatal: error thrown and no exception handler available.
│ InitError(mod=:MbedTLS, error=MethodError(f=typeof(Base.Filesystem.joinpath)(), args=(nothing, "..", "..", "deps", "usr", "lib"), world=0x0000000000006726))
│ rec_backtrace at /buildworker/worker/package_linux64/build/src/stackwalk.c:94
│ record_backtrace at /buildworker/worker/package_linux64/build/src/task.c:246
│ jl_throw at /buildworker/worker/package_linux64/build/src/task.c:577
│ jl_method_error_bare at /buildworker/worker/package_linux64/build/src/gf.c:1616
│ jl_method_error at /buildworker/worker/package_linux64/build/src/gf.c:1634
│ jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2161
│ __init__ at /home/julia/worker/juliapro-release-centos7-0_6/build/tmp_julia/share/julia/stdlib/v1.0/MbedTLS/src/MbedTLS.jl:61
│ jfptr___init___21389 at /home/julia/JuliaPro-1.0.1.1/Julia/lib/julia/sys.so (unknown line)
│ jl_apply_generic at /buildworker/worker/package_linux64/build/src/gf.c:2184
│ jl_apply at /buildworker/worker/package_linux64/build/src/julia.h:1537 [inlined]
│ jl_module_run_initializer at /buildworker/worker/package_linux64/build/src/toplevel.c:90
│ _julia_init at /buildworker/worker/package_linux64/build/src/init.c:813
│ julia_init__threading at /buildworker/worker/package_linux64/build/src/task.c:302
│ main at /buildworker/worker/package_linux64/build/ui/repl.c:227
│ __libc_start_main at /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:310
│ _start at /home/julia/JuliaPro-1.0.1.1/Julia/bin/julia (unknown line)
└ @ Pkg.Operations /home/julia/worker/juliapro-release-centos7-0_6/build/tmp_julia/share/julia/stdlib/v1.0/Pkg/src/Operations.jl:1101

julia> versioninfo()
Julia Version 1.0.1
Commit 0d713926f8 (2018-09-29 19:05 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.0 (ORCJIT, skylake)
Environment:
  JULIA_EDITOR = atom -a
  JULIA_NUM_THREADS = 4
  JULIA_PKG_SERVER = https://pkg.juliacomputing.com/
  JULIA_PKG_TOKEN_PATH = /home/jack/.julia/token.toml

Thanks,

5

Same error message. 2 different computers. both Win10 64. CPUs are i7-5600U and i7-980x (as per original post). And I checked I don’t have JULIA_LOAD_PATH set at all (ENV[“JULIA_LOAD_PATH”] fails )

bunch of packages fail to build. here is the list so far
SpecialFunctions
LLVM
CUDAnative
Conda
FFTW
CuArrays
WebIO
GR
CodecZlib
Plots
CUDAdrv

plain julia (1.0.1) works with no problems. download and build, test all ok.

6

I get the same error when trying to build.

This is the build log:
fatal: error thrown and no exception handler available.
InitError(mod=:MbedTLS, error=MethodError(f=typeof(Base.Filesystem.joinpath)(), args=(nothing, “…”, “…”, “deps”, “usr”, “lib”), world=0x00000000000067f0))
rec_backtrace at /home/Administrator/buildbot/worker/package_win64/build/src\stackwalk.c:94
record_backtrace at /home/Administrator/buildbot/worker/package_win64/build/src\task.c:246
jl_throw at /home/Administrator/buildbot/worker/package_win64/build/src\task.c:577
jl_method_error_bare at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:1616
jl_method_error at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:1634
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2161
init at C:\Users\julia\AppData\Local\Julia-1.0.2\share\julia\stdlib\v1.0\MbedTLS\src\MbedTLS.jl:61
jfptr___init___14286 at C:\Users\Lenovo\AppData\Local\JuliaPro-1.0.2.1\Julia-1.0.2\lib\julia\sys.dll (unknown line)
jl_apply_generic at /home/Administrator/buildbot/worker/package_win64/build/src\gf.c:2184
jl_apply at /home/Administrator/buildbot/worker/package_win64/build/src\julia.h:1537 [inlined]
jl_module_run_initializer at /home/Administrator/buildbot/worker/package_win64/build/src\toplevel.c:90
_julia_init at /home/Administrator/buildbot/worker/package_win64/build/src/home/Administrator/buildbot/worker/package_win64/build/src\init.c:813
julia_init__threading at /home/Administrator/buildbot/worker/package_win64/build/src\task.c:302
wmain at /home/Administrator/buildbot/worker/package_win64/build/ui\repl.c:227
__tmainCRTStartup at /usr/src/debug/mingw64-x86_64-runtime-5.0.3-1/crt\crtexe.c:329
mainCRTStartup at /usr/src/debug/mingw64-x86_64-runtime-5.0.3-1/crt\crtexe.c:212
BaseThreadInitThunk at C:\WINDOWS\System32\KERNEL32.DLL (unknown line)
RtlUserThreadStart at C:\WINDOWS\SYSTEM32\ntdll.dll (unknown line)

This is my setup:
Julia Version 1.0.2
Commit d789231e99 (2018-11-08 20:11 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: Intel(R) Core™ i7-6820HQ CPU @ 2.70GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.0 (ORCJIT, skylake)
Environment:
JULIA_EDITOR = “C:\Users\Lenovo\AppData\Local\JuliaPro-1.0.2.1\app-1.32.2\atom.exe” -a
JULIA_NUM_THREADS = 4
JULIA_PKG_SERVER = https://pkg.juliacomputing.com/
JULIA_PKG_TOKEN_PATH = C:\Users\Lenovo.juliapro\token.toml

I do not have environment variable JULIA_LOAD_PATH

Does anyone have an idea to get this to build?

7

I would try at least Julia 1.0.3 (or Julia 1.2/master or 1.1 as there’s now a release candidate) not just JuliaPro that’s based on older, but wasn’t the issue solved by this comment JuliaPro 1.01.1 crashes on older PC running Windows 10 64-bit - #2 by Zhong_Pan ?

The issue I posted previously has been closed and doesn’t seem relevant to this (MbedTLS) but for those having issues with AVX for OpenBLAS (see start of thread) there’s this open issue (linked from the closed one):

https://github.com/xianyi/OpenBLAS/issues/1947