getsentry / getsentry/sentry-java

Profiler samples are re-anchored once at profile end

未关闭
#5,581 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Platform: Java
主要语言
Kotlin
星标
1.4k
派生
478
平均合并
2 天 23 小时
30 天内合并 PR
67

描述

Audit finding **C1 — theoretical, LOW-MEDIUM**.

`AndroidProfiler` computes `timestampDiff` (the elapsedRealtime↔wall offset) once at profile end and applies it to every wall-stamped `PerformanceCollectionData` sample (`sentry-android-core/src/main/java/io/sentry/android/core/AndroidProfiler.java:309-324`). A wall step during the profile shifts all earlier CPU/memory samples relative to the trace.

Source: [JAVA-557]() §C1.

贡献指南

打开贡献指南

调研方向

Read AndroidProfiler.java at lines 309-324 and trace how timestampDiff is computed at profile end and applied to PerformanceCollectionData samples. Verify the behavior around a wall-clock step during profiling, then ensure earlier CPU and memory samples are not shifted relative to the trace; confirm the corrected timestamp alignment with the relevant profiler coverage.

由索引模型根据 Issue 内容生成。

评估

技术栈
android, java
领域
mobile-dev, performance
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
冷清
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 发到你的邮箱

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