Skip to content

[5.0] clear the DB dirty bit if pinnable_mapped_file fails to fully start#2132

Merged
spoonincode merged 1 commit intorelease/5.0from
reset_dirty_mapped_private_50
Jan 24, 2024
Merged

[5.0] clear the DB dirty bit if pinnable_mapped_file fails to fully start#2132
spoonincode merged 1 commit intorelease/5.0from
reset_dirty_mapped_private_50

Conversation

@spoonincode
Copy link
Contributor

Bumps the chainbase submodule to chainbase's leap-5.0 branch head with AntelopeIO/chainbase#38 fixing #2086

@spoonincode spoonincode linked an issue Jan 24, 2024 that may be closed by this pull request
@spoonincode spoonincode merged commit 2c006cd into release/5.0 Jan 24, 2024
@spoonincode spoonincode deleted the reset_dirty_mapped_private_50 branch January 24, 2024 20:38
@ericpassmore
Copy link
Contributor

Note:start
group: STABILITY
category: BUG
summary: Revs chainbase version to include a bug fix. Leap will now start up cleanly in non-mapped_private mode after failing to startup in mapped_private mode due to lack of swap and/or physical memory.
Note:end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When mapped_private doesn't work, database is left dirty

4 participants