Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-1495

Memory leak in WriteEngineServ

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 1.2.4
    • writeengine
    • None
    • 2019-05

    Description

      There have been a few reports of memory leaks in WriteEngineServ that needs to be investigated. We require valgrind to work properly first (MCOL-1330)

      Attachments

        Issue Links

          is blocked by

          New Feature - A new feature of the product, which has yet to be developed. MCOL-1330 Make ColumnStore work under valgrind

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

          Task - A task that needs to be done. MCOL-3389 Backport MCOL-1495 to 1.1

          • Major - Major loss of function.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Andrew Hutchings (Inactive) made transition -
            Open Closed
            		170d 18h 29m 1
            Roman made transition -
            Closed Stalled
            		141d 2h 24m 1
            Roman made transition -
            Stalled In Progress
            		19h 32m 1
            Roman made transition -
            In Progress In Review
            		6d 6h 14m 1
            Andrew Hutchings (Inactive) made transition -
            In Review In Testing
            		1d 13h 24m 1
            Daniel Lee (Inactive) made transition -
            In Testing Closed
            		1d 4h 31m 1

            People

              dleeyh Daniel Lee (Inactive)
              LinuxJedi Andrew Hutchings (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.