v152 · Storage · IndexedDB
Transaction Race Demo
Launch multiple parallel readwrite transactions each writing a batch of records simultaneously, then read them all back and verify every record persisted. The SQLite backend's write-ahead logging serialises concurrent transactions without data loss — this demo shows that in action.
Chrome 152's SQLite backend uses WAL (write-ahead logging) to handle concurrent writers. Multiple
readwrite transactions queue up; each one commits atomically. No records are silently lost — even under heavy write contention.
—transactions
—expected records
—verified records
—lost records
—total time (ms)
Press "Run concurrent writes" to start the transaction race and verify integrity.
// Events will appear here…
see also
- Write Integrity Test — rapid sequential writes and verify
- Offline Data Vault — practical CRUD app
- Durability Comparison — strict vs relaxed durability modes
- ChromeStatus feature entry — IndexedDB SQLite backend rollout details