blocks|key|4620466|text|作为最佳实践，您应该在不再需要它时立即将其关闭。但是，当垃圾收集离开本地函数作用域时，应该将其标记为清除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4620467|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As a best practice you should close it as soon as you no longer need it. However, garbage collection should mark it for cleanup when it leaves the local function scope.

blocks|key|928997|text|这不是我的强项，但是你应该把StreamWriter放到一个Using()块中，处理流编写器不应该处理流。如果它确实处理了流，你会想要返回streamwriter引用，这样它就可以被进一步清理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|928998|编辑:微软上的伟大的随意编码。StreamWriter不会处理流，因为您可以直接在@ckramer的答案中看到，它确实Close了流。深入研究close方法http://msdn.microsoft.com/en-us/library/system.io.stream.close.aspx|offset|length|style|BOLD|CODE|928999|929000|此方法调用Dispose，指定true以释放所有资源。您不必专门调用Close方法。相反，要确保每个Stream对象都得到了正确的处理。|blockquote|929001|929002|929003|很高兴看到微软直接忽略了他们自己的声明。它会变得更好。|929004|929005|实施者注意事项|929006|929007|在派生类中，不要重写Close方法，而是将所有流清理逻辑放在Dispose方法中。|929008|929009|这完全没有意义。因此，他们不仅会忽略第一条语句，还会创建一个违反Open-Closed原则的类，让您能够以可能导致意外情况的方式修改类。对于这样的陈述，Close绝对不应该是虚拟的，或者他们应该已经修复了这一考虑中的任何推理。|929010|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.io.stream.close.aspx^0|0|0|7|1N|5|26|1V|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@$D|19|E|1A|F|G]|$D|1B|E|1C|F|H]]|9|@$D|1D|E|1E|1|1F]]|A|$]]|$1|I|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1H|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|R|3|S|5|L|7|1M|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]]]

This isn't my strong suit, but yes you should put the StreamWriter into a Using() block, disposing the streamwriter should not dispose the stream. If it does dispose the stream, you'd want to return the streamwriter reference so it could be cleaned up further down.
Edit: Great haphazard coding on Microsoft. The StreamWriter will not dispose the stream as you can directly see on the answer from @ckramer it does <code>Close</code> the stream. Digging into the close method <a href="http://msdn.microsoft.com/en-us/library/system.io.stream.close.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/system.io.stream.close.aspx</a>
<blockquote>
This method calls Dispose, specifying true to release all resources. You do not have to specifically call the Close method. Instead, ensure that every Stream object is properly disposed.
</blockquote>
Great to see Microsoft directly ignoring their own statements. It gets better still.
<blockquote>
Notes to Implementers
In derived classes, do not override the Close method, instead, put all of the Stream cleanup logic in the Dispose method.
</blockquote>
This makes absolutely no sense. So not only do they ignore their first statements, they create a class that violates the Open-Closed principle giving you the capability of modification of the class in ways that can lead to unintended scenarios. For a statement like this, Close should absolutely not be virtual, or they should have fixed whatever reasoning went into this consideration.

blocks|key|2830536|text|如果流不再被引用，那么它肯定会被垃圾收集器处理，因为它实现了IDisposable。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2830537|让垃圾收集器处理它的问题是，它被处理的时刻不是确定的，并且取决于几个条件。|2830538|因此，从理论上讲，它不会导致内存泄漏，但它会使您的应用程序在更长的时间内使用更多的资源，这可能是非常低效的。|2830539|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The stream will surely be disposed by the garbage collector if it is not referenced anymore because it implements IDisposable. 
The problem with letting the garbage collector dispose it is that the moment when it is disposed is not deterministic and depends on several conditions. 
So in theory it won't cause a memory leak but it will make your application use more resources during more time which can be highly inefficient.

blocks|key|4620578|text|只是为了好玩，我打开了反编译器，看看Dispose在StreamWriter上做了什么(认为底层流可能是唯一需要释放的资源)。这就是结果：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4620579|protected+override+void+Dispose(bool+disposing)
{
++++try
++++{
++++++++if+(this.stream+!=+null)
++++++++{
++++++++++++if+(disposing+%7C%7C+(this.Closable+%7C%7C+this.stream+as+__ConsoleStream))
++++++++++++{
++++++++++++++++this.Flush(true,+true);
++++++++++++++++if+(this.mdaHelper+!=+null)
++++++++++++++++{
++++++++++++++++++++GC.SuppressFinalize(this.mdaHelper);
++++++++++++++++}
++++++++++++}
++++++++}
++++}
++++finally
++++{
++++++++if+(this.Closable)
++++++++{
++++++++++++if+(this.stream+!=+null)
++++++++++++{
++++++++++++++++if+(disposing)
++++++++++++++++{
++++++++++++++++++++this.stream.Close();
++++++++++++++++}
++++++++++++++++this.stream+=+null;
++++++++++++++++this.byteBuffer+=+null;
++++++++++++++++this.charBuffer+=+null;
++++++++++++++++this.encoding+=+null;
++++++++++++++++this.encoder+=+null;
++++++++++++++++this.charLen+=+0;
++++++++++++++++base.Dispose(disposing);
++++++++++++}
++++++++}
++++}
}|code-block|syntax|javascript|4620580|有点冗长，但我认为这告诉我们的是，处理流将处理StreamWriter使用的唯一可处置资源。byteBuffer和charBuffer字段是数组，encoding和encoder不是一次性的，基本Dispose是虚拟的，所以如果不清理它，流是唯一会导致问题的东西。|offset|length|style|CODE|4620581|我认为这也清楚地表明，如果你想记录流的内容，并在结束后将其留在一个可用的状态，那么你最挑衅的就是不关闭想要释放你的StreamWriter，因为这将释放流(+Dispose(true))。您还需要确保重置了Stream的位置，因为您无疑会通过读取内容来更改它。当然，这也意味着您可能希望检查流上的CanSeek属性，并确保一旦读取了内容，就能够将位置返回到以前的位置。|4620582|entityMap^0|0|0|1A|A|1L|A|21|8|2A|7|2Q|7|0|27|D|44|7|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]|$I|11|J|12|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@$I|14|J|15|K|L]|$I|16|J|17|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|P|$]]

Just for fun I cracked open the decompiler to look at what Dispose does on a StreamWriter (thinking perhaps the underlying stream is the only resource needed disposed). Here is what came out:

<pre><code>protected override void Dispose(bool disposing)
{
 try
 {
 if (this.stream != null)
 {
 if (disposing || (this.Closable || this.stream as __ConsoleStream))
 {
 this.Flush(true, true);
 if (this.mdaHelper != null)
 {
 GC.SuppressFinalize(this.mdaHelper);
 }
 }
 }
 }
 finally
 {
 if (this.Closable)
 {
 if (this.stream != null)
 {
 if (disposing)
 {
 this.stream.Close();
 }
 this.stream = null;
 this.byteBuffer = null;
 this.charBuffer = null;
 this.encoding = null;
 this.encoder = null;
 this.charLen = 0;
 base.Dispose(disposing);
 }
 }
 }
}
</code></pre>

A bit wordy, but I think what this is telling us is that disposing the stream takes care of the only Disposable resource used by the StreamWriter. The <code>byteBuffer</code> and <code>charBuffer</code> fields are arrays, <code>encoding</code> and <code>encoder</code> are not disposable, and the base <code>Dispose</code> is virtual, so the Stream is the only thing that will cause problems if it is not cleaned up.

I think this also makes it clear that if you are wanting to log the contents of the stream, and leave it in a usable state afterwards, then you most defiantly do not want to dispose your StreamWriter, because that will dispose the Stream (Close calls <code>Dispose(true)</code>). You also want to make sure you reset the position of the Stream since you will no doubt change it by reading the contents. Of course that also means that you probably want to check the <code>CanSeek</code> property on the Stream and make sure that once you read the contents you will be able to return the position to where it was before.

I have method that as follows

<pre><code>public int TranslateOOV(string word, Stream logStream)
{
StreamWriter writer = new StreamWriter(logStream);

//Do some logging
//dont close the writer and leave the caller close the stream
}
</code></pre>

I do not close the StreamWriter as the caller should close the inner stream, does this cause memoryleak?

Is "not disposing StreamWriter" may cause memoryLeak in that case?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有如下方法public int TranslateOOV(string word, Stream logStream){StreamWriter writer = new StreamWriter(logStream);//Do some logging//dont close the writer and leav...

问在这种情况下，“不处理StreamWriter”会导致memoryLeak吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在这种情况下，“不处理StreamWriter”会导致memoryLeak吗？EN