[chasil]

Would a fork of Chromium that was restricted to MISRA-C/C++ offer any real security advantages?

Would parts of Chromium be fundamentally incompatible with these standards?

https://en.wikipedia.org/wiki/MISRA_C

[porphyra]

Sounds very hard. For example, Rule 21.3 in MISRA C 2012 basically prohibits dynamic memory allocation (e.g. malloc, calloc, realloc, free). Implementing a browser with such restrictions would be quite misrable.

[ratmice]

I would think the MISRA rules against dynamic memory allocation would present serious difficulty if not fundamental incompatibility when trying to implement web standards.

[chasil]

It is against the rules to call malloc, yes.

However, it is not against the rules to launch another process with a static amount of declared memory, then access it over shmat().

This is cheating, but could it be safer?

[cyberax]

No.