Memory leak in ImageStreamReader about accord-net-extensions

[dajuric]

Thank you for the comment and for pointing out an possible issue.
Looking at your code, the possible reason (I can think of) why the memory is not freed up because the memory from the generic Image is coped to Bitmap which needs to be disposed.

You mentioned multiple seek operations....
I would be grateful if you could clarify the seek operation usage like:
Did you use the seek operation in a loop ?
Do you show frames randomly (converting them to System.Drawing.Bitmap) ?

(because the seek operation is used in the "ImageExtractionDemo" sample, and I did not find leak there).
So I want to check what operations did you use.....

Thank you again.

Sincerely,
Darko

[sdw1256]

Hi Darco,

I did some chages:

image.Dispose();

reader.Close();

reader.Dispose();

GC.Collect();

GC.WaitForPendingFinalizers();

and now can not see any memory leaks. :)

Thank you !
Best Regards,
Sergei

On Thu, Jan 15, 2015 at 5:59 PM, Darko Jurić [email protected]
wrote:

Thank you for the comment and for pointing out an possible issue.
Looking at your code, the possible reason (I can think of) why the memory
is not freed up because the memory from the generic Image is coped to
Bitmap which needs to be disposed.

You mentioned multiple seek operations....
I would be grateful if you could clarify the seek operation usage like:
Did you use the seek operation in a loop ?
Do you show frames randomly (converting them to System.Drawing.Bitmap) ?

(because the seek operation is used in the "ImageExtractionDemo" sample,
and I did not find leak there).
So I want to check what operations did you use.....

Thank you again.

Sincerely,
Darko

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[dajuric]

You are welcome.

Btw:
you only need to call: reader.Close() and image.Dispose() if the image is System.Drawing.Bitmap