While the base full record and the WT_UPDATE objects are tracked through the WiredTiger cache, when the record's latest version needs to be read, the reader needs to allocate memory and materialize the post-images. Currently this is not tracked and can grow with the number of readers.

Alternatively, this memory usage can be billed to the query, but requires some new APIs from WT to tell how much memory a cursor is using.