Prevent infinite save loop when location is unavailable #3026
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.
Type of change
Description and Context
This bug impacted unsafe saves
When auto save after every change was enabled, an unsafe save to a location that has become unavailable (eg, dismount veracrypt drive), the database modified signal would continually activate a save action that failed. This caused an infinite loop.
When auto-save on exit was enabled, the database tab and the application itself refused to close if saving failed for whatever reason.
The fixes in this commit prevent both of these scenarios from occurring
Fixes Endless Storing when drive is removed #3024
Testing strategy
Tested on Windows using Veracrypt file container
Checklist:
-DWITH_ASAN=ON
. [REQUIRED]