Daniel Micay
Daniel Micay
Our changes may have fixed this issue but if that's the case, it was caused by an AOSP issue where it's unnecessarily harsh to apps which try to use network...
It's already supported via the malloc_object_size APi and it's up to libc if it wants to use it.
@jvoisin Yeah, it's useless with MTE, but we support platforms without MTE so it would make sense to address as a low priority feature.
There are guaranteed guard pages around everything above 16k with the default guard slab internal of 1, so that does provide protection against a lot of attacks even without memory...
The size classes need to be redone for a larger page size. It will be incredibly inefficient doing it that way without redoing it. It would require larger bitmaps for...
It's not set up for pages of that size. For example, 16 byte allocations are placed in a slab with 256 slots, which is 4096 bytes. The slab size will...
It will only happen if a contributor works on it. We have no use for it in GrapheneOS.
Renamed the issue since this isn't specific to Matrix -> Discord but rather happens with anything.
This is fully fixed by https://github.com/42wim/matterbridge/pull/2109 which we've been using in production for a long time.