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: