Handle potential overflow in AllocatorStats

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      We dedicated separate halves of `_bytesAllocated` for allocation and deallocation to avoid undercounting. This result in the value in each half monotonically increasing. Even though int64_t should be enough to account for the current usage of the class (bucket catalog), we should try to reevaluate this when it's used for other use cases in the future.

            Assignee:
            Unassigned
            Reporter:
            Yuhong Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: