# Julia nightly is now filling 2.08 GB of disk space

**URL:** https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939
**Category:** Performance
**Created:** [July 4, 2026, 4:23pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939 "2026-07-04T16:23:03Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 4, 2026, 4:23pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/1 "2026-07-04T16:23:04Z")

</div>

For comparison 1.13 takes 1.08 GB

---

<div class="post-metadata">

### Author: ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [July 4, 2026, 7:06pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/2 "2026-07-04T19:06:11Z")

</div>

```console
$ $ du -hs julia-*
314M julia-1.0.5+0.x64.linux.gnu
609M julia-1.10.11+0.x64.linux.gnu
996M julia-1.11.9+0.x64.linux.gnu
1.1G julia-1.12.6+0.x64.linux.gnu
700M julia-1.12.6+0.x86.linux.gnu
1.1G julia-1.13.0-rc1+0.x64.linux.gnu
425M julia-1.7.3+0.x64.linux.gnu
452M julia-1.8.5+0.x64.linux.gnu
500M julia-1.9.4+0.x64.linux.gnu
1.2G julia-nightly

```

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 4, 2026, 7:09pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/3 "2026-07-04T19:09:19Z")

</div>

![size14](https://global.discourse-cdn.com/julialang/original/3X/b/d/bdbfb4b2eb03951f62dc192ada44c345773f3da3.png)

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 4, 2026, 8:57pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/4 "2026-07-04T20:57:45Z")

</div>

Found out why. The Win installer is shipping the .dylib libs too.

---

<div class="post-metadata">

### Author: ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)
#### Post date: [July 4, 2026, 9:08pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/5 "2026-07-04T21:08:05Z")

</div>

> [@joa-quim](#):
>
> The Win installer is shipping the .dylib libs too.

Sounds like a bug - hopefully won’t be too hard to fix. No sense in shipping macOS libraries on Windows. Is there an open GitHub issue for this?

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 6, 2026, 12:43pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/6 "2026-07-06T12:43:15Z")

</div>

Situation is fixed now.  
Thanks.

---

<div class="post-metadata">

### Author: ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)
#### Post date: [July 6, 2026, 2:19pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/7 "2026-07-06T14:19:53Z")

</div>

> <https://github.com/JuliaLang/julia/issues/62269>
>
> The reason is that it ships the .dylib libs too.

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 15, 2026, 3:49pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/8 "2026-07-15T15:49:19Z")

</div>

Unfortunately it now takes 2.23 GB and no `*.dylib` now. `share\julia\compiled` alone takes 470 MB ???  
I Have no permissions to reopen the issue.

---

<div class="post-metadata">

### Author: ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)
#### Post date: [July 15, 2026, 4:21pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/9 "2026-07-15T16:21:37Z")

</div>

Good thing you found and reported the dylib issue then! 😁

I’ve not been following the recent dev work closely enough to know if this one was an intentional tradeoff or a known transient situation or an unintentional regression. That’s kinda part of using `-nightly`, really. You could open a new issue I suppose, but remember that you are using the unsupported nightly build.

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 15, 2026, 4:43pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/10 "2026-07-15T16:43:23Z")

</div>

Well, yes I can open a new one (and will) but why are original issue authors are not allowed to reopen their issues?  
And, sorry, what do you mean by _unsupported nightly build_?

---

<div class="post-metadata">

### Author: ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)
#### Post date: [July 15, 2026, 4:57pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/11 "2026-07-15T16:57:11Z")

</div>

Well, you can always ask for an issue to be reopened, but in this case I’d say the restriction worked as intended. Since the problem is no longer the dylibs _it’s (potentially) a new issue_.

And, yeah, [nightlies are](https://julialang.org/downloads/manual-downloads/):

> intended as developer previews into the latest work and are not intended for normal use. Most users are advised to use the current stable release version of Julia.

Maybe unsupported isn’t quite the right word, but my point is that they’re not real releases or even release candidates. They have both known and unknown issues. Before I go reporting something against nightly, I try to dig a bit to see if I can identify what changed and if it was intentional. And that’s where this stands in contrast to a release or release candidate: nightlies are developer products and so it’s nice to do some of that dev legwork before filing issues.

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 15, 2026, 5:12pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/12 "2026-07-15T17:12:25Z")

</div>

I know _nightlies_ are not for normal usage. But from time to time I like to see if my stuff has not new problems and mainly, with the more and more vague hope that latencies will start to reduce instead of keeping increasing (compile time. loading time, …)

---

<div class="post-metadata">

### Author: ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)
#### Post date: [July 15, 2026, 5:31pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/13 "2026-07-15T17:31:38Z")

</div>

I think it’s worth opening a new issue. The code in Julia nightly will eventually become the starting point for the next Julia 1.x release, so I think it’s reasonable to keep an eye on it for regressions.

I think a new issue makes more sense than reopening the existing issue, because IIRC the existing issue was about shipping the macOS dylibs on Windows (which IIUC has been fixed).

---

<div class="post-metadata">

### Author: ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 15, 2026, 6:17pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/14 "2026-07-15T18:17:19Z")

</div>

Well, actually the other issue was about suspiciously large file usage, like the current report. It happens that after having raised it I found the reason and added to to the issue (see historical of this thread).

---

<div class="post-metadata">

### Author: ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)
#### Post date: [July 15, 2026, 8:04pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/15 "2026-07-15T20:04:19Z")

</div>

My suspicion is that this might be the new objcache. I noticed it in the release artifacts earlier, but haven’t had the time to look into yet (objcache has a few other high priority items that need addressing).

---

<div class="post-metadata">

### Author: ![langestefan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/langestefan/32/207923_2.png) [@langestefan](https://discourse.julialang.org/u/langestefan)
#### Post date: [July 15, 2026, 8:20pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/16 "2026-07-15T20:20:43Z")

</div>

Can’t spin up a bot these days to do some investigating?

---

<div class="post-metadata">

### Author: ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)
#### Post date: [July 15, 2026, 9:08pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/17 "2026-07-15T21:08:21Z")

</div>

All the bots I can afford are currently busy.

---

<div class="post-metadata">

### Author: ![adienes](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/adienes/32/37459_2.png) [@adienes](https://discourse.julialang.org/u/adienes)
#### Post date: [July 15, 2026, 11:00pm UTC](https://discourse.julialang.org/t/julia-nightly-is-now-filling-2-08-gb-of-disk-space/137939/18 "2026-07-15T23:00:08Z")

</div>

I am (temporarily) not making use of my tokens if someone wants to give me something I can `/goal` and tab out from
