[opensource-dev] ok wtf is this?

[Dave Booth]

On 9/5/2011 12:53 AM, Tateru Nino wrote:

> In order of likelyhood (most to least), I'd say: corrupted texture
> header data, corrupted heap, fragmented heap.
>

After a few moments of reflection of my own, I agree with your 
assessment..  The question that springs to mind is why does it happen in 
an area where I know all the textures have been loaded successfully in 
previous builds without any of the three issues showing up?