Repository navigation
core: skip preload notice on first run - #303
Merged
Merged
Conversation
On a fresh install the chainstate folder is empty or nearly so when Bitcoin Core first starts, so the background cat finishes at once and the "Chainstate preloaded to RAM" notice pops up over the Welcome dialog without telling the user anything useful. Measure the chainstate before preloading and exit quietly when it is under 100 MiB. Later runs, with a real chainstate to load, still show the notice.
This comment has been minimized.
This comment has been minimized.
This was referenced Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Ben · project thread
Before: on a fresh install, "Chainstate preloaded to RAM" pops up right after Bitcoin Core first starts, because the empty chainstate "loads" instantly.
After: the notice is skipped when the chainstate was under 100 MiB when
chainstate-preloadstarted. Later runs with a real chainstate still show it.How:
du -sm chainstateis taken once before the preload loop; the success branch exits quietly below the threshold.Overlaps: #301 changes the icon on the same zenity line (one-line conflict, whichever lands second rebases). #283 removes this notice entirely; if that merges, this PR can be closed.
🤖 Generated with Claude Code
https://claude.ai/code/session_01YWFmpKa9cgSLp61StJJax5
Generated by Claude Code