Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Add profiler markers for activity lifecycle callbacks #21299

Closed
mcomella opened this issue Sep 15, 2021 · 0 comments · Fixed by #21300
Closed

Add profiler markers for activity lifecycle callbacks #21299

mcomella opened this issue Sep 15, 2021 · 0 comments · Fixed by #21300
Assignees
Labels
needs:triage Issue needs triage performance Possible performance wins

Comments

@mcomella
Copy link
Contributor

mcomella commented Sep 15, 2021

These are key events in the application so we should display them in the profiler.

┆Issue is synchronized with this Jira Task

@mcomella mcomella added the performance Possible performance wins label Sep 15, 2021
@mcomella mcomella added this to Needs prioritization in Performance, front-end roadmap via automation Sep 15, 2021
@mcomella mcomella self-assigned this Sep 15, 2021
@mcomella mcomella moved this from Needs prioritization to In progress in Performance, front-end roadmap Sep 15, 2021
@github-actions github-actions bot added the needs:triage Issue needs triage label Sep 15, 2021
mcomella added a commit to mcomella/fenix that referenced this issue Sep 15, 2021
…backs.

We implement these all in the same track because between it'd create a
lot noise between this and fragment lifecycle callbacks.
mcomella added a commit to mcomella/fenix that referenced this issue Sep 15, 2021
…ity.onCreate.

We only instrument onCreate because it's the only one with an
implementation.

While declaring this as a function that accepts a lambda is less
fragile, we've previously had issues with it such as suspected memory
leaks when used for telemetry. Therefore, we go with the simpler
approach.
mcomella added a commit to mcomella/fenix that referenced this issue Sep 15, 2021
…e/Start.

We only instrument these methods because they're the only ones that
noticeably long running in the current implementation.
@mcomella mcomella linked a pull request Sep 15, 2021 that will close this issue
3 tasks
@mergify mergify bot closed this as completed in #21300 Sep 17, 2021
Performance, front-end roadmap automation moved this from In progress to Done Sep 17, 2021
mergify bot pushed a commit that referenced this issue Sep 17, 2021
We implement these all in the same track because between it'd create a
lot noise between this and fragment lifecycle callbacks.
mergify bot pushed a commit that referenced this issue Sep 17, 2021
We only instrument onCreate because it's the only one with an
implementation.

While declaring this as a function that accepts a lambda is less
fragile, we've previously had issues with it such as suspected memory
leaks when used for telemetry. Therefore, we go with the simpler
approach.
mergify bot pushed a commit that referenced this issue Sep 17, 2021
We only instrument these methods because they're the only ones that
noticeably long running in the current implementation.
pkirakosyan pushed a commit to gexsi/user-agent-android that referenced this issue Sep 24, 2021
pkirakosyan pushed a commit to gexsi/user-agent-android that referenced this issue Sep 24, 2021
…ity.onCreate.

We only instrument onCreate because it's the only one with an
implementation.

While declaring this as a function that accepts a lambda is less
fragile, we've previously had issues with it such as suspected memory
leaks when used for telemetry. Therefore, we go with the simpler
approach.
pkirakosyan pushed a commit to gexsi/user-agent-android that referenced this issue Sep 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs:triage Issue needs triage performance Possible performance wins
Development

Successfully merging a pull request may close this issue.

1 participant