diff options
| author | 2022-03-29 20:18:11 +0000 | |
|---|---|---|
| committer | 2022-04-13 18:25:03 +0000 | |
| commit | 6c61f360ec1429da57a78f7918b8c257b203988d (patch) | |
| tree | ef775bbd8fef39257d028a4aaf7c5e66e9bbf6c1 /libs/androidfw/AttributeResolution.cpp | |
| parent | 8e375e4c27393772317d0b3cdbbc5bc6db86850d (diff) | |
Move logging to background thread in LogBuffer
To avoid checking log level settings on the main thread, which can cause jank, move the settings check and logging to a background thread. During manually testing with both the original mechanism and the background thread, messages still appeared in the console with the exact same timestamp (to the millisecond). Nothing I did on the phone was able to get the background thread's BlockingQueue to ever hold more than 3 messages at any given time.
Bug: 221419865
Test: Manually verified messages still logged and BlockingQueue had sufficient capacity
Change-Id: If230e09674dcf1dd7e7b1026e71717f982c5b3d2
Diffstat (limited to 'libs/androidfw/AttributeResolution.cpp')
0 files changed, 0 insertions, 0 deletions