返回由 image.fromstream(stream stream) 方法创建的图像-尊龙凯时

问题描述

我有这个函数，它在使用 image.fromstream 方法创建图像的函数中返回一个图像根据 msdn:

您必须在图像的生命周期内保持流打开

所以我不会关闭流(如果我确实关闭了流，则从返回的图像对象中抛出 gdi 异常).我的问题是当 image.dispose() 在返回的图像上的其他地方被调用时，流是否会关闭/处置

public static image getimage(byte[] buffer, int offset, int count){var memorystream = new memorystream(buffer, offset, count);返回 image.fromstream(memorystream);}

正如其中一个答案所建议的那样，使用不是可行的方法，因为它会引发异常:

public static image getimage(byte[] buffer, int offset, int count){使用(var memorystream = new memorystream(缓冲区，偏移量，计数)){返回 image.fromstream(memorystream);}}public static void main(){var image = getimage(args);图像.保存(路径)；<-- 抛出异常}

1. 根据某些人明确的说法处置/关闭 memorystream 不是必需的，因为它不使用任何非托管资源 其他人说相反的事情所以这是一种进退两难.
2. image.dispose 方法不会处理创建 image 的流
3. image 类不持有对传递给 image.fromstream 方法的 stream 的任何引用，因此该流最终将被 gc 收集...?因此 image.save 方法中的异常
4. 返回一个包装类，其中包含对流的引用和由它创建的图像，从而使我们能够处理这两者......?或者只是使用 tag 属性来保持对父流的引用......?
5. 这个问题似乎只在使用 memorystream 时发生.如果图像是从 connectstream 创建的，即使父流被释放，也不会发生坏.

尽管其他人建议这样做，但在处理图像之前，您不应关闭或处理流.

msdn 指出:><块引用>

您必须在图像的整个生命周期内保持流打开.

对于某些流，例如 memorystream，处置没有太大用处，因为它不分配非托管资源.另一方面，文件流会这样做，因此除非您非常确定流是安全的，否则您应该始终在处理完图像后处理流.

i have this function which returns an image within the function the image is created using the image.fromstream method according to msdn:

you must keep the stream open for the lifetime of the image

so i'm not closing the stream(if i do close the steam a gdi exception is thrown from the returned image object). my question is whether the stream will be closed/disposed when image.dispose() is called somewhere else on the returned image

public static image getimage(byte[] buffer, int offset, int count)
{
    var memorystream = new memorystream(buffer, offset, count);
    return image.fromstream(memorystream);
}

as suggested in one of the answers, using is not the way to go, since it throws an exception:

public static image getimage(byte[] buffer, int offset, int count)
{
    using(var memorystream = new memorystream(buffer, offset, count))
    {
         return image.fromstream(memorystream);
    }
}
public static void main()
{
   var image = getimage(args);
   image.save(path); <-- throws exception
}

1. according to some people explicitly disposing/closing a memorystream is not necessary as it doesn't use any unmanaged resources others say the opposite thing so its kind of a dilemma.
2. image.dispose method doesn't dispose the stream ftom which the image was created
3. the image class doesn't hold any reference to the stream passed to image.fromstream method so the stream will eventually be collected by the gc...? hence the exception in image.save method
4. return a wrapper class which contains a reference to the stream and the image created by it hence enabling us to dispose both of them...? or simply use the tag property to keep a reference to the parent stream...?
5. this problem only seems to happen when using the memorystream. if the image is created from connectstream nothing bad happens even if the parent stream is disposed.

despite what others advice to do, you should not close or dispose the stream until the image is disposed.

msdn states:

you must keep the stream open for the lifetime of the image.

for some streams, like memorystream, disposing doesn't have much use since it doesn't allocate unmanaged resources. file streams on the other hand do, so unless you are very sure the stream is safe, you should always dispose the stream when you are done with the image.