Hello,

We are using Purview C++ SDK to read and apply sensitivity labels on files.

We are suspecting a memory leak when calling Purview file operations. We tested latest 1.14 and 1.15 SDK versions with the same results.

It looks like the memory taken when getting a file handle is never released even though the file operation is done. The file handle is a shared pointer that we are not supposed to manage ourselves and there’s no function available in the SDK to force a release of this handle.

We can provide a very basic example that shows the issue. Most of the code there is taken from the sample provided with the SDK itself.

If you’d like to have that sample project, please let me know. The archive is around 35Mb and you’ll need to have proper build tools (either Linux or Windows) and an Azure application with relevant Purview permissions.

Thanks in advance for the help you can provide to me!

Kind regards,

Olivier

​Hello, We are using Purview C++ SDK to read and apply sensitivity labels on files. We are suspecting a memory leak when calling Purview file operations. We tested latest 1.14 and 1.15 SDK versions with the same results. It looks like the memory taken when getting a file handle is never released even though the file operation is done. The file handle is a shared pointer that we are not supposed to manage ourselves and there’s no function available in the SDK to force a release of this handle. We can provide a very basic example that shows the issue. Most of the code there is taken from the sample provided with the SDK itself.If you’d like to have that sample project, please let me know. The archive is around 35Mb and you’ll need to have proper build tools (either Linux or Windows) and an Azure application with relevant Purview permissions. Thanks in advance for the help you can provide to me! Kind regards, Olivier  Read More

​