Plaidophile

When using refcount-based resource management, make sure that your unlock count matches your lock count.

Yep, we're gonna have to submit again. Meh. (At least, we're pretty sure we will. Nintendo hasn't officially rejected the last build yet. But there's no way they'll be able to play through the game without it crashing.)

12:22 PM Lucky me, it turns out there was another crash bug in code which wasn't mine. Whee.

At least James was gracious enough to not kill his debugger this time, so I could actually investigate. Whee.

Of course, this explains why there was memoryleak behavior but nothing that my memoryleak finder was finding. Because the asset loading layer couldn't be reasonably checked by it. And anyway, it wasn't a memory leak per se, just an asset management leak.

Incidentally, if I hadn't made the asset cache only 512K (for performance reasons) and left it at 1MB, this wouldn't have been a problem.

Also, if I hadn't been distracted while changing some of the sound-management code, this wouldn't have happened.

Meh. I feel crappy now.

Oh well. At least this gives the writers a chance to tweak some last-minute gameflow bugs.