Bug 39896 - StreamImageSource Streams Aren't Disposed
Summary: StreamImageSource Streams Aren't Disposed
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-03-24 18:04 UTC by adamhewitt
Modified: 2016-04-25 18:40 UTC (History)
5 users (show)

Tags: ac
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description adamhewitt 2016-03-24 18:04:16 UTC
Xamarin.Forms.Platform.iOS.StreamImagesourceHandler does not dispose the stream returned from GetStreamAsync. My streams weren't disposing, and I was able to track through the renderers to find the missed using statement there. Notably, the Android equivalent does dispose.
Comment 1 adamhewitt 2016-03-24 18:22:54 UTC
My current workaround is to register a new handler with:

[assembly: ExportRenderer(typeof(StreamImageSource), typeof(StreamImageHandler))]


...where my handler properly disposes. Not a major change, but would obviously be nice for the base platform to handle it for me.
Comment 2 Rui Marinho 2016-03-28 12:18:27 UTC
Should be fixed in 2.2-pre1
Comment 3 adamhewitt 2016-03-28 21:26:46 UTC
Thanks! Is there a listing yet of what else to expect in 2.2?
Comment 4 Parmendra Kumar 2016-04-25 18:40:34 UTC
To verify this issue I have tried to reproduce this issue but I am not able to reproduce it.
Could you please provide me a sample project or steps? so that I can verify this issue efficiently.

Thanks.