If I understand correctly, the idea here is to use `
-fsanitize=array-bounds` in Chromium's `default_compiler_configs`, to add a check for indexing into arrays of known compile time size? The most interesting thing to know is exactly where in Skia this is actually being applied. If I had to guess, this would be hitting SkAlignedStorage.h (and its many direct and indirect users, as well as several other structures like it) quite hard as Skia extensively avoids small heap allocations by having a lot of abstractions over "this code needs to handle arbitrary values but the value is usually 4 or less, so allow that much to go on the stack and only make a heap allocation if more are needed" and then there are still a lot of indexing loops over those (I assume using a range-based for loop would probably avoid this?). In any even this is speculation on my part, but Skia was written around the idea that direct access into small fixed size arrays is fast so it is unsurprising that this should be an issue, but without knowing what the biggest issues are (which transformations are the most expensive) it isn't clear what might be done.