ooni / ooni/probe-multiplatform
Crashes on GrapheneOS with Memory Tagging
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 91
- Forks
- 13
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 28
Description
The app crashes on GrapheneOS when using memory tagging.
here's the crash message:
type: crash
flags: dev options enabled
package: org.openobservatory.ooniprobe:302, targetSdk 36
osVersion: google/mustang/mustang:16/BP4A.260205.001/2026050901:user/release-keys
uid: 10326 (u:r:untrusted_app:s0:c70,c257,c512,c768)
cmdline: org.openobservatory.ooniprobe
processUptime: 185s
signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr e00ce557f508380
threadName: Thread-28
MTE: enabled
backtrace:
/data/app/~~grmSarPQdi71yVE__SCZvg==/org.openobservatory.ooniprobe-sV0pkkCpm6hLNLKkK6uCKw==/base.apk (pc ae3a48)
here's the full process' logs:
OONI Probe log b00a829e8b31.txt
reproducing:
- enable memory tagging in grapheneos
- install app
- run test
- crashes
disabling memory tagging fixes the issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash with memory tagging enabled on GrapheneOS, then inspect the attached OONI Probe process logs and the SIGSEGV backtrace. Done means the app can run the listed test on GrapheneOS with memory tagging enabled without crashing, while preserving behavior when tagging is disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100