commit | d7a694c65f39d7225005187b238fcb7447964b05 | [log] [tgz] |
---|---|---|
author | chaviw <chaviw@google.com> | Mon Mar 21 17:54:23 2022 -0500 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 25 21:35:03 2022 +0000 |
tree | 5dd0a650a56650328fce4216dd74168a349daec8 | |
parent | da21612be5ce676e5e3996e615b3fbce0d7ee66f [diff] |
Use CacheId when buffer is null. It's likely the buffer is null even if eBufferChanged is set because we already cached the buffer. This can happen when the transaction is sent over IPC and we automatically cache the buffer. This change uses the cacheId if the buffer is null Test: Hard to repro Bug: 225815507 Change-Id: Ic95bfc179cc86e494943e9bd6e15cb9afd69f1df (cherry picked from commit dcba9e07976c20bb98a3e92aca149eacc6e59d2d) Merged-In: Ic95bfc179cc86e494943e9bd6e15cb9afd69f1df