03-24-2011, 09:01 AM
Hmm.... what kind of effects should I see with the memory checking switched on, boriel?
I activated memory checking, put the start of the code back to 32768 and recompiled, but I still get the lock-up after my menu has drawn, just the same as without the flag. Moving the ramtop back to 30000 still fixes it, as does reducing the heap size to 2k instead of 4k, so I'm fairly sure it must be memory-related.
This is just a curiosity, by the way - not really a 'problem' as such. I have a lot of extra debug code in my game which I'll be removing, so I'm sure I can get a bunch of memory back quite easily. :-)
I activated memory checking, put the start of the code back to 32768 and recompiled, but I still get the lock-up after my menu has drawn, just the same as without the flag. Moving the ramtop back to 30000 still fixes it, as does reducing the heap size to 2k instead of 4k, so I'm fairly sure it must be memory-related.
This is just a curiosity, by the way - not really a 'problem' as such. I have a lot of extra debug code in my game which I'll be removing, so I'm sure I can get a bunch of memory back quite easily. :-)