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]]

<"Moe Sisko" <null>wrote:

Using dotnet 2.0,

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

Nope.

--
Jon Skeet - <sk***@pobox.com>
Web site: http://www.pobox.com/~skeet
Blog: http://www.msmvps.com/jon_skeet
C# in Depth: http://csharpindepth.com

[Pavel Minaev]

On Jul 11, 9:36*am, Jon Skeet [C# MVP] <[e-mail]:

*<"Moe Sisko" <null>wrote:

Using dotnet 2.0,

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

Nope.

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

[Jeroen Mostert]

Moe Sisko wrote:

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!

--
J.

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Pavel Minaev wrote:

On Jul 11, 9:36 am, Jon Skeet [C# MVP] <[e-mail]:

> <"Moe Sisko" <null>wrote:

>>Using dotnet 2.0,
Just wondering if anyone knows if calling Dispose() on
System.IO.MemoryStream does anything useful.

Nope.

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

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Jeroen Mostert wrote:

Moe Sisko wrote:

>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!

It uses unmanaged resources ?

Arne

[Jeroen Mostert]

Arne Vajhøj wrote:

Jeroen Mostert wrote:

>Moe Sisko wrote:

>>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!

It uses unmanaged resources ?

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

--
J.

[Jeroen Mostert]

Arne Vajhøj wrote:

Jeroen Mostert wrote:

>Moe Sisko wrote:

>>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!

It uses unmanaged resources ?

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

--
J.

[Jeroen Mostert]

Arne Vajhøj wrote:

Jeroen Mostert wrote:

>Moe Sisko wrote:

>>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!

It uses unmanaged resources ?

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

--
J.