On ARMv9a, there’s a new hardware security feature called memory tagging. This is where the CPU cores tag memory to detect out of bounds and use after free bugs. I’m currently running Plexamp on a Pixel 8 pro with grapheneos, which has feature fully built into the allocator. While good for security, this also makes spotting these bugs much easier because the system will kill any apps that try access memory that they shouldn’t.
Interestingly, a few apps (1-2 installed) crash with memory tagging enabled - not immediately but with Plexamp typically in the background while I’m listening to music.
This suggests to me that either in Plexamp or one of its dependencies there’s a memory issue somewhere, either a use after free or out of bounds check failing. Maybe this is worth looking at? Plexamp works fine with tagging explicitly disabled for it, but that obviously takes out the benefits of tagging.
Not sure you can do it in an emulator, but here’s a log from the crash if it helps. Ignore all the complaining for Google play services, it crashes even if they are installed. You can just cmd F for “switch to crash”. Hope this helps somewhat… Plex log 0e57faa9c196.txt (59.4 KB)
I’ve just enabled MTE on my Pixel 8 Pro, and will try and reproduce the issue. Have you got any specific steps to get it to crash? So far playback seems fine, but I’m seeing a buffer overflow crash in the stock Pixel Camera app
Do you have access to logcat on your device, and if so, can you pull out the Plexamp crashes by any chance?
