Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2908

Memory leak in 2.3.16?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.3.16, 2.4.8
    • Fix Version/s: N/A
    • Component/s: N/A
    • Labels:
    • Sprint:
      MXS-SPRINT-104, MXS-SPRINT-105

      Description

      Memory usage of a maxscale instance stayed low for a little less than 24 hours, then went up to about 4GB quickly within a span of ~30 minutes:

      mem1.png shows the memory useage over a full after start, mem2.png the incline over the critical 30min period (note: x axis is in minutes, and y axis in kilobytes, don't let that confuse you)

      This was originally reported against 2.3.9, which had some known leaks, but still seems to happen after upgrade to 2.3.16 (graphs are from 2.3.9)

        Attachments

        1. mem1.png
          mem1.png
          52 kB
        2. mem2.png
          mem2.png
          61 kB

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              hholzgra Hartmut Holzgraefe
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration