Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
[ID: 84651]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides.
See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 746686]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
Devices/Android versions reproduced on: Galaxy S8 (9), Pixel 2 XL (10)
Example project reproducing the issue:
There appears to be a deadlock bug when using abstract suspending database transaction functions.
If the coroutine is cancelled while the transaction is still performing operations, there is a chance that the global Room transaction lock never gets unlocked.
I've replicated this in a small demo project which performs the following
1. Observe the database with a flow, writing it's contents to a simple TextView.
2. Start a coroutine to write to the database within a suspending transaction function + an artificial delay in the transaction.
3. In parallel, delay for less time than the above artificial delay
4. Cancel the above coroutine
5. Attempt to write to the database, observe that the transaction is deadlocked, and further writes to the database are impossible until restarting the application.
This behavior is not observed every try, but I have it looping, and on my two devices - I can encounter it relatively quickly.