GoLand Go Module Cache: Does IDE Clean Up Unused Modules After Closure?

Question

GoLand Go Module Cache
GoLand keeps downloaded modules in ~/.cache/go-build, which can grow during long sessions.
During indexing and code analysis, the IDE may retain HTTP responses and test results, causing temporary memory spikes.
It is unclear whether the IDE automatically purges unused module files when the application exits, or if manual cleanup via Settings is required.
Unresolved behavior: Does GoLand perform automatic cache cleanup on shutdown, and if not, what triggers a purge?
Questions:

Is there a documented automatic cleanup of the Go module cache when GoLand closes?
If not, which events or user actions are needed to trigger cache eviction?
How does the cache cleanup (or lack thereof) affect memory consumption over successive IDE restarts?

Tasadduq Burney · Answer

GoLand does not automatically purge unused Go module cache on shutdown
Confirmed: GoLand retains the on‑disk Go module cache (located at $GOMODCACHE or $GOPATH/pkg/mod) after the IDE is closed; there is no built‑in shutdown routine that deletes unused modules.
What triggers cache eviction

Open Settings → Go → Go Modules and click Clean up unused modules. This removes modules that are not referenced by any currently open project.
Alternatively, run go clean -modcache in a terminal to erase the entire module cache (use with caution).

To verify that no automatic purge occurs, check the cache directory size before and after closing GoLand; unchanged size indicates the IDE did not clean it.
Missing diagnostic detail: Are you using Go Modules mode or the legacy GOPATH mode, and which GoLand version are you running? This determines whether the cleanup UI is present.

GoLand Go Module Cache: Does IDE Clean Up Unused Modules After Closure?

GoLand Go Module Cache

1 answer

GoLand does not automatically purge unused Go module cache on shutdown

What triggers cache eviction

Your perspective belongs here.

0 question comments