The top bit of the xBlockSize member is set to indicate the block is owned by the application. When the block is freed the code checks the top bit is set (as part of a sanity check that the block has not already been freed), then the bit is cleared before the block is added back into the free heap.
So, yes, it is expected that the member will contain a huge number while the block is allocated.