>Jay,
>
>I've had private communication with Staz regarding this phenomenon and the
>bottom line is, from Staz himself, that this is an artifact of how the
>debugger runs within FB. The time to be concerned is when this number
>increases the longer you run your app or the more times you perform some
>particular function within it. For example, if the amount of unrecoverable
>memory went up each time you prepared a gWorld and copied it to the screen
>then you should be concerned about a memory leak associated with that
>function.
>
>Charlie Dickman

Charlie, you may have saved my sanity (or whatever was left of it). Thank 
you.

I never think to look at tech notes until someone mentions them here. Is 
there one about this? Seems like a good candidate--at least for those 
wise enough to actually read them.

Just when I had really taken to heart the message, "The problem is not in 
FB, it's somewhere in your code," I learn that might not always be the 
case. A little disconcerting, but I feel better nonetheless.

 0"0
 =J= a  y
 \_/