Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6694

Memory leak issues when closing with PANIC set

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • Storage - Ra 2020-09-21

      During recovery, if the history store file doesn't exist treat as a recovery failure and it treats as a PANIC error. Due to the PANIC error, during connection close, the memory that is allocated for pages in the cache are leaked.

      Instead of treating the history store file doesn't exist as a recovery error, just verify the history store file before the recovery starts would be good to fix the memory leak.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: