Memory Tagging Causing Crash

未关闭
#64 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Start by reproducing the crash on GrapheneOS Android 17 with memory tagging enabled, then trace the connection startup path into the native Go library, where the backtrace points to internal/bytealg.IndexByteString. The report does not identify a source file or test; determine which dependency or call site reaches that function and inspect available crash logs. Done means the app can attempt a connection without crashing with memory tagging enabled.

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

描述

bug needs investigating
Describe the Bug

This is specific to GrapheneOS, if memory tagging is enabled, on attempting to connect the app will crash with a notification that memory tagging detected an error. Disabling memory tagging allows it continue and not crash.

Crash error:

type: crash
flags: dev options enabled
package: net.pangolin.Pangolin:29, targetSdk 36
osVersion: google/stallion/stallion:17/CP3A.261005.005/2026102101:user/release-keys
uid: 10285 (u:r:untrusted_app_34:s0:c29,c257,c512,c768)
cmdline: net.pangolin.Pangolin
processUptime: 5s

signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr b00c2c1e08d7ea0
threadName: ngolin.Pangolin
MTE: enabled

backtrace:
    /data/app/~~rsu5wcTOSR26iUfYcqQ-5g==/net.pangolin.Pangolin-xXFRcq-UUFSzKzyfDppcYA==/base.apk!libpangolin-go.so (internal/bytealg.IndexByteString+40, pc 60a9e8)
Environment
  • OS Type & Version: GrapheneOS Android 17
  • Pangolin Version: 1.25.3
  • Edition (Community or Enterprise): Enterprise
  • Client Version: 0.8.2
To Reproduce

GrapheneOS with memory tagging enabled, attempt to connect to Pangolin.

AI Disclosure

Nope.

Expected Behavior

App should not crash with memory tagging on and Pangolin should continue to attempt connection.

主要语言
Kotlin
星标
46
派生
15
平均合并
1 分钟
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fosrl/android 的其他 Issue

查看 fosrl/android 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

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