page size % full reporting possibly incorrect

[james cardona]

So I am thinking (I have no concrete proof) that the page % full check that is done during compile is not correct.  I say this because when my machine pages start to go into the 90% full range I begin to have page fault bugs and unexplained and goofy run time bugs.  As soon as I move things around to go below 90% on all my pages the bugs go away.  I am sure that all my code has proper declarations and page attributes so this is clearly something that is occurring where pages are somehow writing into each other.
Jim

[Brian Dominy]

I looked at this again and I don't see anything wrong with the check itself.  I know it has saved me a few times, and I've run with ~99% in some pages before with no trouble.

Do you have any other evidence?  Does it happen with the same page or multiple pages?  Does it fail at a predictable time or randomly?

Is your image ROM too big?  That's one thing I noticed, if you have too many images it could overwrite parts of the first section of code.  I never put as many images into my games as you.

Brian 

On Tue, Nov 19, 2013 at 1:02 PM, james cardona <JAMES....@pseg.com> wrote:

So I am thinking (I have no concrete proof) that the page % full check that is done during compile is not correct.  I say this because when my machine pages start to go into the 90% full range I begin to have page fault bugs and unexplained and goofy run time bugs.  As soon as I move things around to go below 90% on all my pages the bugs go away.  I am sure that all my code has proper declarations and page attributes so this is clearly something that is occurring where pages are somehow writing into each other.
Jim

--
 
---
You received this message because you are subscribed to the Google Groups "FreeWPC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freewpc+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
- Brian

[james cardona]

sorry.  Didn't mean to sound accusational.  It could be something else like too many fast ram variables or something.  When I figure it out I will report back.  Only thing I know for sure is that my code is too big somewhere.