diff options
| author | 2022-07-13 00:48:56 +0000 | |
|---|---|---|
| committer | 2022-07-13 01:30:10 +0000 | |
| commit | 84859cb0783fc6d3dc514b1f0a439358705630c6 (patch) | |
| tree | 928138d6bed41ae753bcba1cfeae65354c4e0807 /libs/gui/LayerDebugInfo.cpp | |
| parent | b763b1493a1c54746cf5580cd7894474d987d4d1 (diff) | |
libbinder: detect bad linkToDeath
If linkToDeath is called without any threads listening for binder
transactions, then it may not be served. This is a hard to debug
issue, so adding a log.
Bug: 237730299
Test: boot, and see these logs (they occur in cameraserver which sets
up the threadpool late. this is not an issue, but the ordering could
be 'nicer'):
07-12 20:52:26.537 515 515 W BpBinder: Linking to death on android.app.IActivityManager but there are no threads (yet?) listening to incoming transactions. See ProcessState::startThreadPool and ProcessState::setThreadPoolMaxThreadCount. Generally you should setup the binder threadpool before other initialization steps.
07-12 20:52:26.673 515 515 W BpBinder: Linking to death on android.hardware.ISensorPrivacyManager but there are no threads (yet?) listening to incoming transactions. See ProcessState::startThreadPool and ProcessState::setThreadPoolMaxThreadCount. Generally you should setup the binder threadpool before other initialization steps.
Change-Id: I8c2bb308f4bd479000e644a785d8c27341ad496a
Diffstat (limited to 'libs/gui/LayerDebugInfo.cpp')
0 files changed, 0 insertions, 0 deletions