Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-39113

addr2line stack trace resolver deterimental in MariaDB-backup and MSAN/ASAN builds

    XMLWordPrintable

Details

    • Not for Release Notes

    Description

      From https://github.com/MariaDB/buildbot/pull/933, in a MSAN/ASAN test environment, the addr2line was so high in memory utilization (anon-rss:14320664kB) that it was the pick of the OOM killer to resolve the OOM situation.

      It addition to its harmful effects, it resolution is of such a poor quality compared to a) the implementation of the sanitizers themselves, b) the core dump and gdb resolution that is most common for these environments that use these instrumented builds.

      A simple solution is to default stack-trace to 0 for the ASAN/MSAN builds.

      MariaDB-backup also forces the enabling of stack-trace. Disabling this unconditionally reduces the risk of a user operational impact if a stack trace starts in a mariabackup critical locked period.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDBF-1185 msan/ubsan/asan with clang 22

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-40349 MSAN Builds: slow stack trace on crash delays or prevents core file writing

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDBF-1194 Reduce the memory pressure of hz-bbw8 and hz-bbw9

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-29568 libelf (specificly libdw) based stack resolver

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32363 when InnoDB gets an assertion failure, WSREP layer is not handled gracefully

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21010 Mariadb hangs (during a backtrace), stops responding to new connections

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-40349 MSAN Builds: slow stack trace on crash delays or prevents core file writing

          • Major - Major loss of function.
          • Closed

          Activity

            People

              danblack Daniel Black
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 5h
                  5h

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.