# Julia v1.3.0-rc4 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965>\
**Category:** Announcements\
**Tags:** release\
**Created:** [October 16, 2019, 2:00am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965 "2019-10-16T02:00:45Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![pazzo83](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pazzo83/32/232_2.png) [@pazzo83](https://discourse.julialang.org/u/pazzo83)\
**Post date:** [October 21, 2019, 8:32pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/21 "2019-10-21T20:32:22Z")

</div>

Is anyone getting frequent freezes in the REPL? I was not seeing this in rc3, not sure what it’s related to (seems to happen when I am using the CSV package).

---

<div class="post-metadata">

**Author:** ![Tero\_Frondelius](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tero_frondelius/32/7629_2.png) [@Tero\_Frondelius](https://discourse.julialang.org/u/Tero_Frondelius)\
**Post date:** [October 22, 2019, 7:36am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/22 "2019-10-22T07:36:09Z")

</div>

@yuyichao was right, after fixing [JuliaFEM/Materials.jl#55](https://github.com/JuliaFEM/Materials.jl/issues/55) the build passes on all platforms, see [JuliaFEM/UMAT.jl#14](https://github.com/JuliaFEM/UMAT.jl/pull/14).

---

<div class="post-metadata">

**Author:** ![xanfus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xanfus/32/5813_2.png) [@xanfus](https://discourse.julialang.org/u/xanfus)\
**Post date:** [October 23, 2019, 10:38am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/23 "2019-10-23T10:38:39Z")

</div>

Windows 10 1903 build 18362.418. Atom 1.40.1.  
I’ve experienced irreproducible memory leakages, endless task spawns at stage of package compilation. At times i switched from rc2 to rc4 without killing Julia session and memory leakage started.

```julia
Julia Version 1.3.0-rc4.1
Commit 8c4656b97a (2019-10-15 14:08 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: AMD A8-6410 APU with AMD Radeon R5 Graphics
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, btver2)
Environment:
  JULIA_EDITOR = "C:\Users\acer\AppData\Local\atom\app-1.40.1\atom.exe" -a
  JULIA_NUM_THREADS = 4

 [c52e3926] Atom v0.11.1
  [6e4b80f9] BenchmarkTools v0.4.3
  [e5e0dc1b] Juno v0.7.2
  [37b6cedf] Traceur v0.3.0
  [b8865327] UnicodePlots v1.1.0

```

I’ve just executed _versioninfo()_ and _status_ at Pkg prompt and everything is nominal. No such erroneus behaviour is observed at Ubuntu Mate 18.04.5 with rc4. Today i’ve observed, REPL hasn’t quit being busy at the latter system without any evident task assigned. But sole press on “Enter” freed the REPL.

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [October 23, 2019, 12:25pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/24 "2019-10-23T12:25:40Z")

</div>

> [@xanfus](#):
>
> At times i switched from rc2 to rc4 without killing Julia session

I am really curious how you did that.

---

<div class="post-metadata">

**Author:** ![xanfus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xanfus/32/5813_2.png) [@xanfus](https://discourse.julialang.org/u/xanfus)\
**Post date:** [October 23, 2019, 1:08pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/25 "2019-10-23T13:08:51Z")

</div>

> [@Tamas\_Papp](#):
>
> > At times i switched from rc2 to rc4 without killing Julia session
> 
> I am really curious how you did that.

I’m sorry. I set particular Julia executable through ‘julia-client’ package settings. v1.3.0-rc2 session wasn’t killed automatically, nor, i assume, v1.3.0-rc4.1 was patched through, which was highly unlikely, just as you stated, but memory leakage had pronounced itself at that time.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 23, 2019, 3:05pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/26 "2019-10-23T15:05:01Z")

</div>

I would like to emphasize that as much as reporting and discussing issues here is appreciated, it is not a substitute for filing an issue on github with a reproducer. Bugs that are only posted here are unlikely to get fixed.

---

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [October 24, 2019, 6:15pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/27 "2019-10-24T18:15:40Z")

</div>

What about precompilation times or first run times?  
I’ve read it’s going to be faster but I haven’t found more details.

---

<div class="post-metadata">

**Author:** ![Karajan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/karajan/32/8545_2.png) [@Karajan](https://discourse.julialang.org/u/Karajan)\
**Post date:** [October 24, 2019, 6:55pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/28 "2019-10-24T18:55:49Z")

</div>

Yes, it’s “going to” as in “not yet (in this release), but in the nearish future (maybe even next release), now that threading is getting closer to being finished”.

---

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [October 25, 2019, 9:16am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/29 "2019-10-25T09:16:38Z")

</div>

I had a trouble adding several packages at once (starting with 1.3-rc1), resulting in the following error. I then break the set of packages to install into smaller subsets and all went ok, and now I do no longer have this error.  
In julia-1.2 I did manage to get the whole set at once.:

```julia
(v1.3) pkg> update
  Updating registry at `~/.julia/registries/General`
  Updating git-repo `https://github.com/JuliaRegistries/General.git`
 Resolving package versions...
  Updating `~/.julia/environments/v1.3/Project.toml`
 [no changes]
  Updating `~/.julia/environments/v1.3/Manifest.toml`
 [no changes]

(v1.3) pkg> add JSON2 XLSX Cxx PyCall RCall DataFrames BenchmarkTools IndexedTables Pipe Plots StatsPlots CSV JuMP GLPK Ipopt SymPy LsqFit Weave ZipFile Interact Plots Mux
 Resolving package versions...
ERROR: MethodError: Cannot `convert` an object of type Pkg.Types.VersionSpec to an object of type VersionNumber
Closest candidates are:
  convert(::Type{T}, ::T) where T at essentials.jl:168
Stacktrace:
 [1] convert(::Type{Union{Nothing, VersionNumber}}, ::Pkg.Types.VersionSpec) at ./some.jl:34
 [2] Pkg.Types.PackageEntry(::String, ::Pkg.Types.VersionSpec, ::Nothing, ::Bool, ::Pkg.Types.GitRepo, ::Nothing, ::Dict{String,Base.UUID}, ::Nothing) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Types.jl:259
 [3] #PackageEntry#26(::String, ::Pkg.Types.VersionSpec, ::Nothing, ::Bool, ::Pkg.Types.GitRepo, ::Nothing, ::Dict{String,Base.UUID}, ::Nothing, ::Type{Pkg.Types.PackageEntry}) at ./util.jl:722
 [4] (::Core.var"#kw#Type")(::NamedTuple{(:name, :version, :pinned, :tree_hash, :path, :repo),Tuple{String,Pkg.Types.VersionSpec,Bool,Nothing,Nothing,Pkg.Types.GitRepo}}, ::Type{Pkg.Types.PackageEntry}) at ./none:0
 [5] update_manifest!(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Operations.jl:93
 [6] #add#102(::Bool, ::Pkg.BinaryPlatforms.Linux, ::typeof(Pkg.Operations.add), ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}, ::Array{Base.UUID,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/Operations.jl:977
 [7] #add at ./none:0 [inlined]
 [8] #add#25(::Bool, ::Pkg.BinaryPlatforms.Linux, ::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Pkg.API.add), ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:102
 [9] add(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/API.jl:72
 [10] do_add!(::Dict{Symbol,Any}, ::Array{Pkg.Types.PackageSpec,1}, ::Dict{Symbol,Any}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/REPLMode.jl:505
 [11] #invokelatest#1(::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::typeof(Base.invokelatest), ::Any, ::Any, ::Vararg{Any,N} where N) at ./essentials.jl:709
 [12] invokelatest(::Any, ::Any, ::Vararg{Any,N} where N) at ./essentials.jl:708
 [13] do_cmd!(::Pkg.REPLMode.Command, ::REPL.LineEditREPL) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/REPLMode.jl:412
 [14] #do_cmd#23(::Bool, ::typeof(Pkg.REPLMode.do_cmd), ::REPL.LineEditREPL, ::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/REPLMode.jl:391
 [15] do_cmd at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/REPLMode.jl:387 [inlined]
 [16] (::Pkg.REPLMode.var"##28#31"{REPL.LineEditREPL,REPL.LineEdit.Prompt})(::REPL.LineEdit.MIState, ::Base.GenericIOBuffer{Array{UInt8,1}}, ::Bool) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/Pkg/src/REPLMode.jl:619
 [17] #invokelatest#1 at ./essentials.jl:709 [inlined]
 [18] invokelatest at ./essentials.jl:708 [inlined]
 [19] run_interface(::REPL.Terminals.TextTerminal, ::REPL.LineEdit.ModalInterface, ::REPL.LineEdit.MIState) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/REPL/src/LineEdit.jl:2306
 [20] run_frontend(::REPL.LineEditREPL, ::REPL.REPLBackendRef) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/REPL/src/REPL.jl:1039
 [21] run_repl(::REPL.AbstractREPL, ::Any) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.3/REPL/src/REPL.jl:201
 [22] (::Base.var"##774#776"{Bool,Bool,Bool,Bool})(::Module) at ./client.jl:390
 [23] #invokelatest#1 at ./essentials.jl:709 [inlined]
 [24] invokelatest at ./essentials.jl:708 [inlined]
 [25] run_main_repl(::Bool, ::Bool, ::Bool, ::Bool, ::Bool) at ./client.jl:374
 [26] exec_options(::Base.JLOptions) at ./client.jl:312
 [27] _start() at ./client.jl:468

```

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [October 26, 2019, 6:24am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965/30 "2019-10-26T06:24:31Z")

</div>

As noted above, unless you open an issue there is a significant chance that this will be lost in the noise. (If you already opened an issue, then please disregard).

[Previous page](https://discourse.julialang.org/t/julia-v1-3-0-rc4-is-now-available/29965.md?page=1)