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

Memory leaks in mysqlbinlog

    XMLWordPrintable

Details

    Description

      The mysqlbinlog tool is leaking memory, causing failures in various tests when compiling and testing with AddressSanitizer or LeakSanitizer like this:

      cmake -DCMAKE_BUILD_TYPE=Debug -DWITH_ASAN:BOOL=ON /path/to/source
      make -j$(nproc)
      cd mysql-test
      ASAN_OPTIONS=abort_on_error=1 ./mtr --parallel=auto
      

      5.5 e07118946a82af60c7cc3804c321d3fd9a49f128

      CURRENT_TEST: rpl.rpl_row_mysqlbinlog
       
      =================================================================
      ==8988==ERROR: LeakSanitizer: detected memory leaks
       
      Direct leak of 112 byte(s) in 1 object(s) allocated from:
          #0 0x4eff87 in __interceptor_malloc (/dev/shm/5.5/client/mysqlbinlog+0x4eff87)
          #1 0x60eaab in my_malloc /mariadb/5.5/mysys/my_malloc.c:41:10
          #2 0x5300dd in Log_event::read_log_event(char const*, unsigned int, char const**, Format_description_log_event const*, char) /mariadb/5.5/sql/log_event.cc:1568:12
          #3 0x564a9c in dump_remote_log_entries(st_print_event_info*, char const*) /mariadb/5.5/client/mysqlbinlog.cc:1978:17
          #4 0x536408 in dump_log_entries(char const*) /mariadb/5.5/client/mysqlbinlog.cc:1794:21
          #5 0x535e4b in main /mariadb/5.5/client/mysqlbinlog.cc:2505:18
          #6 0x7f71ea0a1b16 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x22b16)
      

      Attachments

        Issue Links

          Activity

            People

              sujatha.sivakumar Sujatha Sivakumar (Inactive)
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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