[Mono-bugs] [Bug 79665][Blo] Changed - System.IO.Compression OutOfMemory exception
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri Oct 20 17:24:42 EDT 2006
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by esanchezfo at gmail.com.
http://bugzilla.ximian.com/show_bug.cgi?id=79665
--- shadow/79665 2006-10-20 13:12:01.000000000 -0400
+++ shadow/79665.tmp.14843 2006-10-20 17:24:42.000000000 -0400
@@ -73,6 +73,32 @@
Please provide a self-contained test case, preferably
as a console application, just to be sure the bug is
not in ASP.NET itself.
Prio changed (see http://bugzilla.ximian.com/bug_status.html#priority)
+
+------- Additional Comments From esanchezfo at gmail.com 2006-10-20 17:24 -------
+I test that is problem of System.IO.Compression Namespace.
+
+I change the code to use the ICSharpCode library (that comes with
+Mono) and the code works fine.
+
+using ICSharpCode.SharpZipLib.Zip.Compression;
+using ICSharpCode.SharpZipLib.Zip.Compression.Streams;
+
+// ..
+
+if (context.Request.Headers ["Accept-encoding"].Contains ("deflate"))
+{
+ context.Response.AppendHeader ("Content-encoding", "deflate");
+ context.Response.Filter = new DeflaterOutputStream
+(context.Response.Filter, new Deflater (Deflater.DEFAULT_COMPRESSION,
+true));
+}
+
+// ..
+
+And of course testing the first option (with System.IO.Compression)
+over .NET (Microsoft) 2.0 work fine too.
+
+Thanks.
More information about the mono-bugs
mailing list