-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Julia 1.0.5 large memory usage compiling module #38634
Comments
odow
added a commit
to jump-dev/JuMP.jl
that referenced
this issue
Dec 1, 2020
…nd a compiler bug The upstream issue is logged at: JuliaLang/julia#38634 StaticArrays should be removed as a direct dependency once support for Julia 1.0.x is removed.
odow
changed the title
Julia 1.0.5, Linux, OutOfMemory error
Julia 1.0.5 large memory usage compiling module
Dec 1, 2020
This may not be a bug, just some optimizations of large unions that haven't been/won't be back ported to 1.0.x, an so probably requires a fix on our end. Feel free to close if this seems correct. |
This was referenced Dec 1, 2020
odow
added a commit
to jump-dev/JuMP.jl
that referenced
this issue
Dec 2, 2020
Add StaticArrays as a dependency and cap maximum version to work-around a compiler bug. The upstream issues are logged at: - JuliaLang/julia#38634 - JuliaArrays/StaticArrays.jl#857 StaticArrays should be removed as a direct dependency once support for Julia 1.0.x is removed.
Closed by JuliaArrays/StaticArrays.jl#859 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
JuMP is failing tests on GitHub Actions, Julia 1.0.5 (but notably, not on Julia 1.5) due to the v1.0 release of StaticArrays. I've simplified it to the one below. Here's the relevant issue jump-dev/JuMP.jl#2390.
The underlying issue is that running
using Foo
takes more than 4 GB of memory, and so GitHub Actions spikes the VM.Compiling with Julia 1.5 uses ~42 MiB.
I'm not sure what the resolution is. In the interim, we can cap our StaticArrays version. But this is fairly brittle. If 1.6 becomes LTS soon-ish, we could also just drop support for 1.0 and forget about this.
Here's the output
cc @mlubin
The text was updated successfully, but these errors were encountered: