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

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?