8 Aug
2025
8 Aug
'25
2:45 p.m.
On Fri Aug 8 14:45:14 2025 +0000, Connor McAdams wrote:
Hm. I guess it could in theory lead to us reading out of bounds? There are quite a few tests for file size validation in d3dx9, so I assumed it's probably something that has been encountered somewhere. It might make sense to succeed in the image info case, but fail if an application tries to load it into a texture. Or fail in both cases, I don't have a strong opinion either way, and don't know of an application that relies upon this behavior.
Right, I guess it's more relevant for the texture load case. I guess it doesn't matter for now but I'd rather avoid potential out of bounds during texture loads until proven necessary (and the `WARN()` should hopefully help with spotting that).