| commit | 6cdbb537105b663572e71afe06bde1164fc215f3 | [log] [tgz] |
|---|---|---|
| author | Jiwen 'Steve' Cai <jwcai@google.com> | Fri Jun 02 15:23:26 2017 -0700 |
| committer | Jiwen 'Steve' Cai <jwcai@google.com> | Fri Jun 02 15:26:01 2017 -0700 |
| tree | 8149204577ec2ed75dd8aa2d9294ddeb9b34d631 | |
| parent | cb496acbe593326e8d5d563847067d02b2df40ec [diff] |
No crash from AHardwareBuffer_unlock on NULL fence The API document states: "If fence is not NULL then it will be set to a file descriptor that is signaled when all pending work on the buffer is completed." As it's too late to change the document, we should probably update the implement and use GraphicsBuffer::unlock under the hood. Bug: 62302267 Test: Build, AHardware CTS Change-Id: Ic0fac5d7addfba67baaa1b5d7c221fc25d02df56