getsentry / getsentry/sentry-java

Create performance issue for IPC calls on main thread

Open
#4,264 0 comments 0 reactions 0 assignees View on GitHub
Android Feature Spans
Dominant language
Kotlin
Stars
1.4k
Forks
478
Avg merge
2d 23h
Merged PRs (30d)
67

Description

### Description

Whenever there is an IPC call on the main thread, this could cause app to freeze.
From [Android docs](https://developer.android.com/topic/performance/vitals/render#scheduling-delays):

`Often, binder calls—the inter-process communication (IPC) mechanism on Android—cause long pauses in your app's execution. On later versions of Android, it's one of the most common reasons for the UI thread to stop running. Generally, the fix is to avoid calling functions that make binder calls. If it's unavoidable, cache the value or move work to background threads. As codebases get larger, you can accidentally add a binder call by invoking some low-level method if you aren't careful. However, you can find and fix them with tracing`

To do so, we should identify all method calls of interest and add a new profiling issue

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.