Open Bug 1386481 Opened 7 years ago Updated 2 years ago

[Storage] ROLLBACK after COMMIT failed - no transaction is active

Categories

(Firefox for iOS :: Data Storage, defect)

All
iOS
defect

Tracking

()

People

(Reporter: rnewman, Unassigned)

Details

(Whiteboard: [MobileCore][DataLoss])

https://sentry.prod.mozaws.net/operations/firefox-ios-rk/issues/632562/

ROLLBACK after failed COMMIT failed. Error code: 1, Error Domain=org.mozilla Code=1 "SQL error or missing database cannot rollback - no transaction is active" UserInfo={NSLocalizedDescription=SQL error or missing database cannot rollback - no transaction is active}

No stack.

This should never occur.
The only way I see this happening:

1. We have two callers simultaneously sharing a connection, such that one has closed their shared transaction by the time the other tries to roll back.

2. A writer has been interrupted via sqlite3_interrupt. Interruption automatically rolls back an open transaction.

3. We are somehow having the database be closed and reopened during our write. Closing a connection automatically rolls back an open transaction.
As discussed with Richard, we need to do an audit of the code to determine if we are accidentally nesting transactions anywhere.
Whiteboard: [MobileCore][DataLoss]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.