getsentry / getsentry/sentry-java

Create performance issue for IPC calls on main thread

Aperta
#4,264 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Android Feature Spans
Lingua principale
Kotlin
Stelle
1.4k
Fork
478
Merge medio
2g 23h
PR unite (30g)
67

Descrizione

### 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

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.