You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the MediaInfoWrapper class to handle media file information in my application, I encounter a significant memory leak issue. Below is a snippet of the code:
var mediaInfo = new MediaInfoWrapper(filePath, _logger);
double totalSeconds = TimeSpan.FromMilliseconds(mediaInfo.Duration).TotalSeconds;
int roundedSeconds = (int)Math.Round(totalSeconds);
I need to process 2860 media files, and I've noticed that the MediaInfoWrapper instances are not disposed of after their usage. Unfortunately, the MediaInfoWrapper class does not implement the IDisposable interface, which exacerbates the memory management issues. This oversight leads to increased memory consumption and potential application instability over time.
Could the implementation be updated to include IDisposable, or could another mechanism for proper resource management be provided?
Thank you.
The text was updated successfully, but these errors were encountered:
When using the MediaInfoWrapper class to handle media file information in my application, I encounter a significant memory leak issue. Below is a snippet of the code:
var mediaInfo = new MediaInfoWrapper(filePath, _logger);
double totalSeconds = TimeSpan.FromMilliseconds(mediaInfo.Duration).TotalSeconds;
int roundedSeconds = (int)Math.Round(totalSeconds);
I need to process 2860 media files, and I've noticed that the MediaInfoWrapper instances are not disposed of after their usage. Unfortunately, the MediaInfoWrapper class does not implement the IDisposable interface, which exacerbates the memory management issues. This oversight leads to increased memory consumption and potential application instability over time.
Could the implementation be updated to include IDisposable, or could another mechanism for proper resource management be provided?
Thank you.
The text was updated successfully, but these errors were encountered: