Does calling MemoryStream.Dispose() do anything ?

[Moe Sisko]

Using dotnet 2.0,

Just wondering if anyone knows if calling Dispose() on
System.IO.MemoryStream does anything useful.

 

[Jon Skeet [C# MVP]]

Using dotnet 2.0,

Just wondering if anyone knows if calling Dispose() on
System.IO.MemoryStream does anything useful.

Nope.

 

[Pavel Minaev]

Nope.

Who knows, maybe it will in a future version of .NET... personally, I
still put all mine in using() anyway.

 

[Jeroen Mostert]

Just wondering if anyone knows if calling Dispose() on
System.IO.MemoryStream does anything useful.

Yes, it calls Stream.Dispose(), which in turn will dispose an event created
as a result of calling asynchronous methods (.BeginRead(), .BeginWrite())
if they were not all finished before the stream was finalized.

So you better call .Dispose(), or you might leak a single event handle in
very unlikely circumstances!

 

[Arne Vajhøj]

Who knows, maybe it will in a future version of .NET... personally, I
still put all mine in using() anyway.

I can not imagine MemoryStream ever holding unmanaged data.

But I still agree with the conclusion: call Dispose on anything
that implements IDisposable is a good thing.

Arne

 

[Arne Vajhøj]

Yes, it calls Stream.Dispose(), which in turn will dispose an event
created as a result of calling asynchronous methods (.BeginRead(),
.BeginWrite()) if they were not all finished before the stream was
finalized.

So you better call .Dispose(), or you might leak a single event handle
in very unlikely circumstances!

It uses unmanaged resources ?

Arne

 

[Jeroen Mostert]

It uses unmanaged resources ?

Indirectly, yes. But only in the circumstances described above.