diff options
| author | Emilian Peev <epeev@google.com> | 2021-10-04 18:27:14 -0700 |
|---|---|---|
| committer | Emilian Peev <epeev@google.com> | 2021-10-08 19:48:12 +0000 |
| commit | dd55b3dee558ff83f286d3abacfbd1a0c9d31278 (patch) | |
| tree | 9c5f127f6efcc8c1c90c260d926a531cae7455a4 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 77794d27c64af8e271abbb701832924956c9c216 (diff) | |
Camera: Avoid possible deadlock when closing advanced extension session
The advanced extension session request processor must not hold the
'mInterfaceLock' when calling the camera device implementation as it
could result in a deadlock with the camera device close that can
run at the same time and try to acquire the same locks in reverse order.
The request processor will only read from 'mCameraConfigMap' which is
initialized only once during session setup and will not change during
the session lifetime.
A sample stack trace will look like this:
Service thread:
1) android.hardware.camera2.impl.CameraCaptureSessionImpl.stopRepeating
2) android.hardware.camera2.impl.CameraAdvancedExtensionSessionImpl$RequestProcessor.stopRepeating
Client thread:
1) android.hardware.camera2.impl.CameraAdvancedExtensionSessionImpl.release
2) android.hardware.camera2.impl.CameraDeviceImpl.close
Bug: 202074988
Test: Manual using application,
Camera CTS
Change-Id: If992667a7d7e54be5bea1fcc4b1d71ec1b895ca0
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions