-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Root cause PR_TAGGED_ADDR_ENABLE
failures on Pixels
#962
Comments
Hi, which PR is missing? The next release is imminent. Everything looks okay (except for some hard to track down bugs). |
#856. The app is randomly closing itself and not restarting. It's very annoying. |
(going by temporal analysis) v054c released on May 6. The patch you submitted was merged on Apr 14. You sure that patch isn't already in the released v054c version? |
You are right. Maybe #966 would do the trick? 🤔 |
Is this similar to #893? Or, is it about the app crashing (due to bugs)? I'm confused how |
I think it is closed due to memory pressure, so perhaps on #893. This is on a Pixel though. |
Following up, it looks like it was actually crashing (a few times a day). Sent the bug report to your email. |
Thanks for sending along a bugreport. Can you confirm if you sent it from |
Yes that's me. |
@Mygod, Could you please confirm which email you sent the bug report to? We can't seem to find it in our inboxes. |
It's hello at celzero dot com? |
Found both the emails. Thanks. |
By the time I check last night, the files were gone though. If you can reshare it... Sorry that this has been a bit too cumbersome for you. |
Weird. Resent. Sorry! |
It seems that the issue causing is similar to issue #786. The error message in the logs suggests that address tagging aka However, disabling Memory Tagging Extension (MTE) on Rethink (per #786 Alternatively, this command achieves same result:
We don't have Pixel devices for ourselves to test this. If you are okay, will you please let me know if it helped in any way? |
|
Maybe there is actually use-after-free/buffer-overflow in your code instead? Are there other cgo/android repos that have this issue? |
Use after free, and buffer overflow exists in gomobile / cgo output of I don't think If only these logs were any helpful... I'm generally surprised that switching off |
It looks like if you run it in SYNC mode the logs will be more helpful. https://source.android.com/docs/security/test/memory-safety/arm-mte#sync-mode |
In my limited experience elsewhere with ASAN / MSAN / TSANs... debug modes are painfully slow (: (on that note, I see a few |
You can send a debug mode apk to me and I can try to grab some logs. :) |
PR_TAGGED_ADDR_ENABLE
failures on Pixels
Did you receive the crash report? |
I can no longer use this app after updating to Android 14.
|
How long? I miss my pr.
The text was updated successfully, but these errors were encountered: