JoTech It's expected that the bug persists. The purpose of utilizing the new toggle "memory tagging in vendor processes" is to make memory tagging produce a nice crash log during reproduction of the issue, if there is a memory issue. It would help debug the problem. You would get a notification saying "Memory tagging detected an issue in [process]", and tapping on "More info" would present a crash log.
Am I right in assuming that you have not gotten such a notification while you reproduced the bug, in the latest Alpha/Beta version of GrapheneOS (2024042200) with the new toggle "memory tagging in vendor processes" enabled?