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

Memory leak on MariaDB 5.5.31

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 5.5.31
        • Fix Version/s: 5.5.32
        • Component/s: None
        • Labels:
          None
        • Environment:
          2 Quad Intel Xeon 2,2 Ghz - 12 GB memory OS : CentOS 5.8

          Description

          I migrated from MySQL 5.1 to MariaDB 5.5.31 on many servers during three last months. On some servers, i see a big change i consumer memory which requires a stop-start of MariaDB to release memory. The size of data evolves very little. The attachments illustrate the change since the migration of one server made on 05/28/2013. Thank for your help.

            Gliffy Diagrams

              Attachments

              1. engine_memory_usage.txt
                1.0 kB
              2. engine_memory_usage.txt
                1.0 kB
              3. memory_usage (3 Months).PNG
                memory_usage (3 Months).PNG
                58 kB
              4. my.cnf
                2 kB
              5. prdmutmys002.zip
                1.78 MB
              6. screenshot-1.jpg
                screenshot-1.jpg
                125 kB
              7. show_global_status.txt
                26 kB
              8. show_variables.txt
                178 kB
              9. swap_usage (3 Months).PNG
                swap_usage (3 Months).PNG
                47 kB

                Issue Links

                is blocked by

                Task - A task that needs to be done. MDEV-4763 5.5.32 merge

                • Blocker - Blocks development and/or testing work, production could not run.
                • Closed
                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-4703 Memory leak in MariaDB 5.5.31

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

                Web Link Bug #1170103 - Memory leak @ read_view_open_now (read0read.c:152/166) in Percona Server 5.5.30-30.2 GA

                  Activity

                  Ascending order - Click to sort in descending order
                  12 older comments
                  Hide
                  Permalink
                  pendexgabo Gabriel Sosa added a comment -

                  how is turning off the query cache a solution here? Sounds like removing an totally relevant part of the performance component of the server...

                  Show
                  pendexgabo Gabriel Sosa added a comment - how is turning off the query cache a solution here? Sounds like removing an totally relevant part of the performance component of the server...
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment -

                  It's not a solution, it's a workaround till the next release (5.5.32) where the bug is supposed to be fixed.

                  Show
                  elenst Elena Stepanova added a comment - It's not a solution, it's a workaround till the next release (5.5.32) where the bug is supposed to be fixed.
                  Hide
                  Permalink
                  pendexgabo Gabriel Sosa added a comment -

                  Looks like you guys just release the version 5.5.32 and this fix is not on it. Do you have any certain release date for this bugifx? Also would you help guys if we provide us some more info on this matter ?

                  thanks

                  Show
                  pendexgabo Gabriel Sosa added a comment - Looks like you guys just release the version 5.5.32 and this fix is not on it. Do you have any certain release date for this bugifx? Also would you help guys if we provide us some more info on this matter ? thanks
                  Hide
                  Permalink
                  elenst Elena Stepanova added a comment - - edited

                  The fix should be in 5.5.32 release. The bug was fixed in XtraDB 5.5.32 (at least it is marked as such in https://bugs.launchpad.net/percona-server/+bug/1170103), and MariaDB 5.5.32 includes XtraDB 5.5.32.

                  We didn't have a reproducible test case to verify it, so please re-open the issue (or comment on it to get it re-opened) if you still have the problem with MariaDB 5.5.32,

                  Show
                  elenst Elena Stepanova added a comment - - edited The fix should be in 5.5.32 release. The bug was fixed in XtraDB 5.5.32 (at least it is marked as such in https://bugs.launchpad.net/percona-server/+bug/1170103 ), and MariaDB 5.5.32 includes XtraDB 5.5.32. We didn't have a reproducible test case to verify it, so please re-open the issue (or comment on it to get it re-opened) if you still have the problem with MariaDB 5.5.32,
                  Hide
                  Permalink
                  pendexgabo Gabriel Sosa added a comment -

                  excellent! perfect. Thanks for your time

                  Show
                  pendexgabo Gabriel Sosa added a comment - excellent! perfect. Thanks for your time

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      psujet SUJET
                    • Votes:
                      2 Vote for this issue
                      Watchers:
                      9 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: