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

mcsapi memory leak - destructor not called from swig generated code

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • 1.1.4, 1.2.0
    • Icebox
    • None
    • None

    Description

      Swig causes a memory leak as objects are not deconstructed. This can crash an application if many ColumnStoreBulkInserts are initialized but never freed.

      I assume that Swig can't handle object creation ala

      createBulkInsert() and createSystemCatalog() and only implements correct memory management for objects instantiated with new ColumnStoreDriver / pymcsapi.ColumnStoreDriver()...

      It seems to work to call the destructor through Swig directly if a memory leak is identified.
      e.g. for ColumnStoreBulkInsert in Python one can manually call:

      bulk.__swig_destroy__(bulk)
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jens.rowekamp Jens Röwekamp (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.