Damus: 1.17 (1331)
Steps
- Run
testAppLifecycleRaceConditions
Analysis
During testing, testAppLifecycleRaceConditions is exiting with "signal abort" due to a reader transaction leak assertion getting hit.
It is currently unclear whether this configures a real reader transaction leak or if the debug assertion logic is incomplete.
What is likely happening is that the txn deinit path (which closes the transaction) is timing out because ndb is closed at that point in time, which means it will never leave the debug array ndb_debug_query_txns, and the debug mechanism detects that as a reader leak.
This is not necessarily a reader leak, because LMDB might automatically close reader transactions when it restarts.
Furthermore, given that the app no longer actively closes/opens the database to follow app foreground/background modes, this present low risk for reader transaction leaks during normal operation. The biggest issue is probably CI failure noise.
Damus: 1.17 (1331)
Steps
testAppLifecycleRaceConditionsAnalysis
During testing,
testAppLifecycleRaceConditionsis exiting with "signal abort" due to a reader transaction leak assertion getting hit.It is currently unclear whether this configures a real reader transaction leak or if the debug assertion logic is incomplete.
What is likely happening is that the txn deinit path (which closes the transaction) is timing out because ndb is closed at that point in time, which means it will never leave the debug array
ndb_debug_query_txns, and the debug mechanism detects that as a reader leak.This is not necessarily a reader leak, because LMDB might automatically close reader transactions when it restarts.
Furthermore, given that the app no longer actively closes/opens the database to follow app foreground/background modes, this present low risk for reader transaction leaks during normal operation. The biggest issue is probably CI failure noise.