Developer Console: Memory: Conflicting measurements & Huge Untracked (On a Default Baseplate)

Help and Feedback Scripting Support
1

There appears to be multiple problems with Memory Statistics.

image
image1073×245 70.2 KB

Upon immediately joining a place, the Memory Stat (implied total; nesting CoreMemory) is somehow less than CoreMemory. Either these measurements are wrong, or they are asynchronous. Which is it?

Only after around a minute will this discrepancy sort out for the map Default Baseplate.

Furthermore, in a live game of mine, Memory is only 700MB when PlaceMemory is 500MB and CoreMemory is 300MB, and unlike on the BasePlate this does not resolve.

image
image1165×168 44 KB

Untracked memory relaxes at a perfect zero, and then, for no discernible reason suddenly is allocated some 80-88MB on a flux? On a Baseplate.

I get the impression to disregard this altogether, and only pay attention to PlaceMemory. Am I wrong to do so?

2

Untracked memory is memory queued up to be garbage collected, and it will go down as soon as the server needs more space

Its where memory goes to die…

1 Like