Files
AnyOldName3 0877c22458 Constrain the maximum number of a particular warning per file
A corrupt mesh file could cause the warning to be logged up to uint32_t max times.
We cannot log four billion warnings without a large performance cost.

According to https://gitlab.com/OpenMW/openmw/-/work_items/9024, a corrupt mesh in BCOM could trigger this at least four million times, which triggered the freeze catcher.

This is completely untested, but at least it compiles and I remembered to run the formatter.
2026-03-23 18:06:19 +00:00
..