Trial running PR testing with MALLOC_CHECK_=2 to catch memory issues earlier.

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines, Storage Engines - Persistence
    • None
    • None

      We recently suffered a double free bug that should've been caught by tooling well before it spawned 10+ bug tickets resulting from undefined behaviour. 

      One of the ways we plan to catch these failure modes in the future is to run python testing under ASAN per WT-15513. However that is very heavyweight, it is possible that the malloc_check flags may be used and more efficient, thus something we can use for PR testing. 

      Scope:

      • Evaluate performance impact of MALLOC_CHECK_
      • Enable for PR testing or mainline testing.

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

              Created:
              Updated:
              Resolved: