This is most likely due to the way in which the TrueLog On Error has been generated. The TrueLog On Error information can either be stored for one complete transaction or based on content history. These settings can be found under SETTINGS | ACTIVE PROFILE | RESULTS | TRUELOG. Under the Store TrueLog setting there are two options: For one transaction Based on content history (default) For One Transaction Tracks the whole erroneous transaction and not just the relevant pages (history). As the memory consumption is extremely dependent on the length of the transaction, this option should only be used when memory is of no concern or the transaction is rather short. Based On Content History Stores just the relevant pages (history) to the error which occurs, and drops the pages that are no longer relevant from memory. This helps with memory consumption. Of course the amount of memory required is still dependent on the size of the pages in the history. Old KB# 19256
↧
