Java requests memory from the OS in large chunks and then gives it out to the app in smaller chunks.
Well, one of two things happened:
magic gremlins are adding magic compression in your computer.
something else was freed at the same time to make room for it so you didn’t see an accurate increase.
…I know where my money is going.
Whatever you are trying to do… there is no sure fire accurate way to do it. You could call System.gc() four or five times before loading the texture if you really wanted the best possibility of seeing memory grow accurately but it still might not.
One thing is sure, there is no magic memory wormhole in your system so it’s got to be a sensor issue.