-
Notifications
You must be signed in to change notification settings - Fork 624
Fireperf: fix screen trace in multi-activity apps #3311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Coverage Report 1Affected Products
Test Logs
Notes |
Size Report 1Affected Products
Test Logs
Notes |
/retest |
/run binary-size |
/test check-changed |
firebase-perf/src/main/java/com/google/firebase/perf/application/AppStateMonitor.java
Show resolved
Hide resolved
jeremyjiang-dev
approved these changes
Mar 3, 2022
visumickey
approved these changes
Mar 7, 2022
jeremyjiang-dev
pushed a commit
that referenced
this pull request
Mar 9, 2022
* mstop screen trace in onPause * onActivityPostPaused * fix test * fix test typo * add debug message
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
b/210055697
Cause:
In multi-activity apps, when Activity 1 starts Activity 2,
FrameMetricsAggregator
does not work whenframeMetricsAggregator.add(activity2)
is called beforereset()
of activity1. That is the current behaviour because we useonStart
andonStop
. The order of these lifecycle callbacks are well defined in the activity lifecycle documentation, "Coordinating activities" section.Fix:
Move the "stopping of screen traces" from
onActivityStopped
toonActivityPostPaused
. According to the same documentation, the order of these callbacks are well defined, and it is guaranteed that activity 1'sonPause
will happen before activity 2'sonStart
.The reason
onActivityPostPaused
is picked overonActivityPaused
is becauseonActivityPaused
is called at the beginning ofonPause
, andonPause
then calls each fragment'sonPause
. Ifreset()
is called inonActivityPaused
, then the last fragment in the activity won't have a chance to read its frame metrics.Consequence:
Fragment screen traces must use
onPause
instead ofonStop
becauseframeMetricsAggregator.reset()
is moved fromonStop
toonPause
.