diff options
| author | 2022-05-03 14:36:40 -0500 | |
|---|---|---|
| committer | 2022-05-03 14:36:40 -0500 | |
| commit | 63238fe68480ca6a3ecd31e6e3edb1c24c949e21 (patch) | |
| tree | 65b50e3345441b3c86a1e3bdd38d9f62300b6ac9 /libs/androidfw/StringPool.cpp | |
| parent | c15af2cb878df47707c2689a85e58cb457fa4e23 (diff) | |
Don't request sync again for reparented WC
When a WC is reparented, a sync request can be initiated again to
account for any config changes. However, this can cause deadlocks in the
client since the app may already have produced a sync buffer and that
buffer is now held in a sync transaction. The app can't produce any more
buffers since it has ran out and just gets stuck waiting. The previous
buffer will never get applied since BLASTSyncEngine is waiting for the
next buffer to return from the sync request.
Disable the second sync request for now and handle a real solution
later.
Test: No ANR in split gmail + messages on 60hz device
Bug: 214320347
Change-Id: I5e11925de848781ddc34793f118b739703cc8ca2
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions