Flush accepted tab moves before replacement restoration
This commit is contained in:
@@ -40,14 +40,19 @@ publication are still required; this lane did not deploy or restart anything.
|
||||
|
||||
## Replacement-owner write ordering
|
||||
|
||||
A disposed owner skips writes that have not started, including operations queued
|
||||
behind another storage owner. Already-started operations share a small per-key
|
||||
read/write order with replacement owners; replacement reads wait for an old
|
||||
in-flight write before merging and saving newer navigation. Idle operation keys
|
||||
are removed, and a failure never poisons later operations.
|
||||
Accepted navigation snapshots enter the shared per-key operation order
|
||||
immediately. Disposal rejects new records and late read-back writes, but does
|
||||
not discard a valid last move that was already queued. Replacement reads wait
|
||||
for all previously accepted writes before merging and saving newer navigation.
|
||||
This preserves the last move when an app is recreated without a new choice,
|
||||
while newer replacement navigation still wins. Idle operation keys are removed,
|
||||
and a failure never poisons later operations.
|
||||
|
||||
18 focused tab/controller/full-app navigation cases passed after this follow-up
|
||||
(`/tmp/memwatch/out.hBbm4Y`), including a blocked old write plus a queued old write,
|
||||
disposal, replacement navigation and delayed release. The newer state wins for
|
||||
both an in-memory store and distinct SharedPreferences store instances sharing
|
||||
a logical key. Two independent ordering-helper tests passed (`out.FffOAC`).
|
||||
21 focused controller/full-app navigation/ordering cases passed after the final
|
||||
follow-up (`/tmp/memwatch/out.ksAW8x`); analyzer clean (`JMtEk8`). Regressions
|
||||
cover a blocked old write plus a queued accepted old write, disposal, replacement
|
||||
navigation and delayed release. Older accepted history is written before the
|
||||
replacement loads it; newer navigation wins afterward. Recreating without a new
|
||||
choice restores the old owner's last accepted chat, not its previous Settings
|
||||
location. Both same-instance fake stores and distinct SharedPreferences store
|
||||
instances sharing one logical key are covered.
|
||||
|
||||
Reference in New Issue
Block a user