mirror of
https://github.com/OpenMW/openmw.git
synced 2026-05-06 07:56:40 -04:00
0877c22458
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.