Fixed
Status Update
Comments
ia...@gmail.com <ia...@gmail.com> #2
This is affecting CameraView as well.
yb...@google.com <yb...@google.com>
yb...@google.com <yb...@google.com> #3
Bugjuggler: wait until next quarter
yb...@google.com <yb...@google.com> #4
Hi. I've received your bug and will wait until 2020-01-01 00:00 -0800 PST and then assign the bug to ericng@google.com.
ia...@gmail.com <ia...@gmail.com> #5
Hello,
A fix has been applied for most cases in Alpha08 (Dec 18th release), however we are keeping this open for a more robust fix to come. Thanks.
A fix has been applied for most cases in Alpha08 (Dec 18th release), however we are keeping this open for a more robust fix to come. Thanks.
ap...@google.com <ap...@google.com> #7
Bugjuggler:
ap...@google.com <ap...@google.com> #8
Hi. I've received your bug and will wait for b/146048690 to be fixed and then assign the bug to ericng@google.com.
Description
withContext(Dispatchers.Default) {
db.beginTransaction()
db.insert(data) // DAO suspend function
db.update(anotherData) // DAO suspend function
db.setTransactionSuccessful()
db.endTransaction()
}
This can deadlock because transaction are exclusive and are ThreadLocal, meaning once a transaction is started in a thread form the default dispatcher, another coroutine dispatcher thread will get blocked even if we are within the same coroutine.