summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Riddle Hsu <riddlehsu@google.com> 2022-08-22 17:18:09 +0800
committer Riddle Hsu <riddlehsu@google.com> 2022-08-22 09:25:57 +0000
commit2f37c0d5cf151a882aa25521afb149c745a163f6 (patch)
treed5b5f4b42c891b50b06860a12aabba1df6fc33f2 /libs/androidfw/StringPool.cpp
parent0054cebd125015cbfe2ae7a0c104483ee0f043e1 (diff)
Avoid misleading log while warm launch
When launch a new activity on an existing process, the original code will let the activity with lastLaunchTime=0 go through setProc -> addActivityIfNeeded -> setLastActivityLaunchTime. And because the existing process has mLastActivityLaunchTime>0, the method will print a confusing log. So just move the assignment of lastLaunchTime before setProcess. And remove the later setLastActivityLaunchTime because setProcess has already called it. Bug: 243164648 Test: Launch an activity and calls finish(), and then launch it again. There should not have a warning log: "Tried to set launchTime (0) < mLastActivityLaunchTime". Change-Id: Id767a0589cbb7d9730a3deceb12789341391cdff
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions