summaryrefslogtreecommitdiff
path: root/tools/aapt2/diff/Diff.cpp
diff options
context:
space:
mode:
authorPavel Grafov <pgrafov@google.com>2017-03-23 15:17:52 +0000
committerPavel Grafov <pgrafov@google.com>2017-03-28 16:37:49 +0000
commitcb3df3bf4a9777af4e9c4337eb7318bca6d22dee (patch)
treeab63a2a78ace91aea177ab4962a4faf119ba2d43 /tools/aapt2/diff/Diff.cpp
parent759922d9db7183347ea4fd4be8319b8cc6f6b611 (diff)
Store up to 5 network log batches if needed.
In the normal mode when the DO fetches the logs ASAP, there will still be no more than one last full batch in memory at once. If the DO is too slow, or the broadcast queue is too crowded we will store up to 5 of them, discarding older ones when there are more than 5. Also the batch gets discarded 5 minutes after it has been retrieved or another more recent batch has been retrieved. Previously the last batch would stay in memory until the next one is ready. But it seems unreasonable for the DO to rely on it since there are no guarantees. This would probably even save some memory under normal conditions on average. Bug: 35753013 Test: cts-tradefed run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.DeviceOwnerTest#testNetworkLoggingWithSingleUser Change-Id: Ib8e91a98103d804375cb0d7423f93175b4b9bcb6 (cherry picked from commit 48733074d7ba80755e40432b7ff02b66e27d3edb) Merged-in: Ib8e91a98103d804375cb0d7423f93175b4b9bcb6
Diffstat (limited to 'tools/aapt2/diff/Diff.cpp')
0 files changed, 0 insertions, 0 deletions