Fix spurious "Timeout waiting for provider"
There is a race that if two clients are acquiring the same content provider at the same momment, the second one would create a new ContentProviderRecord and then start a new process. Bug: 148953992 Test: Manual Change-Id: I3e95be32208a0869dc0b399da70f767abdd76fb4
Loading
Please register or sign in to comment