Determine cause of Palite indirect leak LSan failure

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      In order to merge the checkpoint size feature branch we suppressed any functions with the name palite_, this is a very wide reaching suppression and not one I'd like to have for long. However the cause of the leak is not obvious and not something we should block the feature branch on.

      An example test failure is: https://spruce.mongodb.com/task/wiredtiger_checkpoint_size_amazon2023_arm64_asan_unit_test_bucket06_64e6fb89859d7780c956d742576b1bca093981e5_26_02_13_17_23_38?execution=0

      It notes:

      Total: 639,136 bytes leaked in 377 allocations across 226 distinct stack traces 

      Scope:

      • Disable the suppression, run unit-test-bucket06 in the relevant variant
      • If it reproduces attempt to determine cause

            Assignee:
            Unassigned
            Reporter:
            Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: