Since upgrading to 1.11 I’ve been receiving messages about cache misses like this one: julia> using GLMakie [ Info: Precompiling GLMakie [e9467ef8-e4e7-5192-8a1a-b1aee30e663a] (cache misses: invalid header (8)) and this: julia> using Verify Precompiling Verify... 1 dependency successfully preco…

Here’s a proposal to change “invalid header” to “incompatible header”. rename: invalid -> incompatible cache header JuliaLang:master ← IanButterworth:ib/invalid_to_incompatible opened 07:45PM - 18 O…

@kristoffer.carlsson can correct me if I’m wrong but I think this is just additional information about stuff that was happening already anyway. That is, when using a package sometimes Julia will find that a precompilation file created for that package can’t be loaded from the cache for some reason,…

That sounds reasonabIe. I should clarify that I felt like packages were taking longer to load/cache misses happening more often but that might just be a feeling since I’m being told about it now by Pkg.

Wouldn’t it just be better to not print anything by default? It is not that most user can do anything with that information anyway. It does give the impression that something is broken.

That’s not something that one who does want to understand why precompilation is being triggered can retrieve afterwards.

I’ve also wondered about this message. It gives the incorrect impression that something has gone wrong, and there’s nothing the average user can, or should, do in response to the message. For beginning Julia programmers this will be confusing, and for experienced programmers it’s noise almost always…

But couldn’t it be triggered by a julia command line argument?

I think that’s what it used to be. Just from personal experience there’s a lot of hard-to-make-precise griping from people - myself included - about excessive recompilation. When it happens to me I usually (in the nicest possible way) blame Kristoffer, who reasonably asks me for a reproducer. The p…

in that case you’d have to Ctrl-C to kill the current pre-compilation, and that may change the reason for the NEXT pre-compilation, so you still can’t know why it WAS pre-compiling, I think?

Can someone clarify - if I don’t follow the advice of @ianshmean , and I do a bunch of activate switching on various projects, use of various packages in my startup.jl etc. etc., will I still get the correct versions of packages loaded, and the annoyance is just that I might get too much recompilati…

Cache misses when 'using' packages since upgrading to 1.11

General Usage

giordano October 18, 2024, 10:11am 4

“invalid header” also probably sounds a little bit scarier than it was intended to be, maybe “incompatible header” would be a nicer wording.

Topic		Replies	Views
Module X with build ID Y is missing from the cache. This may mean X [Z] does not support precompilation but is imported by a module that does General Usage precompilation	6	122	March 6, 2026
Precompile package causing missing-from-cache errors New to Julia precompilation	0	1150	March 11, 2019
Package keeps precompiling after starting Julia every single time Performance	2	263	April 11, 2024
0.7: The call to compilecache failed to create a usable precompiled cache General Usage	0	979	August 9, 2018
How to debug incomplete precompilation New to Julia precompilation	12	387	September 9, 2025

Cache misses when 'using' packages since upgrading to 1.11

Related topics