getsentry / getsentry/sentry-java

Create performance issue for IPC calls on main thread

未关闭
#4,264 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Android Feature Spans
主要语言
Kotlin
星标
1.4k
派生
478
平均合并
2 天 23 小时
30 天内合并 PR
67

描述

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

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。