# Julia v1.3.0-rc2 is now available
**URL:** https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837
**Category:** Announcements
**Tags:** release
**Created:** [September 17, 2019, 3:11am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837 "2019-09-17T03:11:46Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@ararslan](https://discourse.julialang.org/u/ararslan)
#### Post date: [September 17, 2019, 3:11am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/1 "2019-09-17T03:11:46Z")
The second release candidate for Julia v1.3.0 is now available. Get binaries for Linux (i686, x86-64, ARMv7, AArch64), FreeBSD (x86-64), Windows (32-, 64-bit), and macOS at [Download Julia](https://julialang.org/downloads). Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.3.0-rc2/NEWS.md) to see what will be new in 1.3.0 and see the list of commits included since 1.3.0-rc1 [here](https://github.com/JuliaLang/julia/compare/v1.3.0-rc1...v1.3.0-rc2).
As a release candidate, this should **not** be considered production-ready; it’s intended to give users a chance to try out their code with 1.3.0 prior to a full release. Note that 1.3 on Travis AppVeyor, and Cirrus CI now points to 1.3.0-rc2.
The versioning for the 1.3 prereleases is [a bit misleading](https://discourse.julialang.org/t/julia-v1-3-0-rc1-is-now-available/27673/10) (my fault), so even though this is labeled a release candidate, we know it won’t be the last RC; we’re already working on [the next one](https://github.com/JuliaLang/julia/pull/33221). Apologies for the confusion, but do note that 1.3 is feature frozen, so any remaining changes in these RCs are simply bugfixes.
As usual, let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues) if you run into any issues.
---
### Author:  [@ufechner7](https://discourse.julialang.org/u/ufechner7)
#### Post date: [September 18, 2019, 10:48pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/2 "2019-09-18T22:48:58Z")
I have a complex piece of code that fails on 1.3RC2. But I think I wait for RC3 before creating an issue. Simplifying this code to provide a MWE will be difficult.
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [September 18, 2019, 10:53pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/3 "2019-09-18T22:53:20Z")
Can you share the code with a Manifest to snapshot the versions of dependencies?
---
### Author:  [@ufechner7](https://discourse.julialang.org/u/ufechner7)
#### Post date: [September 22, 2019, 3:50am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/4 "2019-09-22T03:50:08Z")
Created a bug report: [https://github.com/JuliaLang/julia/issues/33358](https://github.com/JuliaLang/julia/issues/33358)
---
### Author:  [@lbilli](https://discourse.julialang.org/u/lbilli)
#### Post date: [September 23, 2019, 8:04pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/5 "2019-09-23T20:04:32Z")
This might be a little premature, but I noticed a substantial increase in the memory footprint of Julia v1.3 compared to v1.2/1.1.
In particular, I have some simple code that makes few thousands `http` requests, parse `json` responses and store the results in an array of `DataFrame`s.
The same code performs similarly in Julia v1.1/1.2/1.3, with the exception of the RAM used, which in v1.3 ends up being about twice as much that of v1.1/1.2.
Is this expected?
---
### Author:  [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)
#### Post date: [September 24, 2019, 12:02am UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/6 "2019-09-24T00:02:47Z")
Can you post a reproducer?
---
### Author:  [@yakir12](https://discourse.julialang.org/u/yakir12)
#### Post date: [September 24, 2019, 3:01pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/7 "2019-09-24T15:01:47Z")
`versioninfo()` returns `rc1` in the `rc2` binaries:
```julia
julia> versioninfo()
Julia Version 1.3.0-rc1.0
Commit 768b25f6a8 (2019-08-18 00:04 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: AMD Ryzen Threadripper 2950X 16-Core Processor
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, znver1)
```
---
### Author:  [@oschulz](https://discourse.julialang.org/u/oschulz)
#### Post date: [September 24, 2019, 3:21pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/8 "2019-09-24T15:21:52Z")
I get
```julia
julia> versioninfo()
Julia Version 1.3.0-rc2.0
Commit a04936e3e0 (2019-09-12 19:49 UTC)
```
---
### Author:  [@lbilli](https://discourse.julialang.org/u/lbilli)
#### Post date: [September 24, 2019, 5:29pm UTC](https://discourse.julialang.org/t/julia-v1-3-0-rc2-is-now-available/28837/9 "2019-09-24T17:29:00Z")
As an update, I tried to manually invoke `GC.gc()` and the difference in memory usage significantly decreased to around 20%.
So, I guess this is not really an issue but it has more to do with differences in how memory is allocated and garbage collected.