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

main.sp test fails for embedded server

    XMLWordPrintable

Details

    Description

      The test main.sp that was enhanced by wlad in MDEV-20699 would fail on 10.3 and 10.4 with embedded. This might be a sign of a memory leak

      ./mtr --embedded main.sp

      like this:

      --- /mariadb/10.3/mysql-test/main/sp.result	2021-09-29 15:08:31.711087544 +0300
      		 
      +++ /mariadb/10.3/mysql-test/main/sp.reject	2021-10-04 11:08:53.851498265 +0300
      		 
      @@ -8913,6 +8913,6 @@
      		 
       0
      		 
       SELECT VARIABLE_VALUE-@global_mem_used FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME='MEMORY_USED';
      		 
       VARIABLE_VALUE-@global_mem_used
      		 
      -0
      		 
      +1888
      		 
       DROP PROCEDURE sp1;
      		 
       # End of 10.3 tests

      On merge to 10.5, I had already disabled this part of the test. Possibly this part of the test will have to be rewritten as MDEV-26723.

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20699 mysqldump of routines causes MariaDB to get killed by oom-killer

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26723 Cached stored procedures are counted as global memory, should be session memory

          • Major - Major loss of function.
          • Open

          Activity

            People

              shulga Dmitry Shulga
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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