mirror of
https://github.com/adamhathcock/sharpcompress.git
synced 2026-02-08 21:21:57 +00:00
ArgumentOutOfRangeException on Zip expansion #143
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dkekesi on GitHub (Nov 7, 2016).
I get the following exception when expanding a certain Zip archive:
System.ArgumentOutOfRangeException: Stream length must be non-negative and less than 2^31 - 1 - origin.
Parameter name: value
at System.IO.MemoryStream.set_Position(Int64 value)
at SharpCompress.Common.Zip.ZipHeaderFactory.ReadHeader(UInt32 headerBytes, BinaryReader reader)
at SharpCompress.Common.Zip.SeekableZipHeaderFactory.GetLocalHeader(Stream stream, DirectoryEntryHeader directoryEntryHeader)
at SharpCompress.Common.Zip.SeekableZipFilePart.LoadLocalHeader()
at SharpCompress.Common.Zip.SeekableZipFilePart.GetCompressedStream()
at SharpCompress.Archives.IArchiveEntryExtensions.WriteTo(IArchiveEntry archiveEntry, Stream streamToWriteTo)
Can you look into what the problem may be? Other programs can expand the Zip. The file itself is merely 300K in size.
Thanks.
@adamhathcock commented on GitHub (Nov 8, 2016):
Need an example ZIP to see the problem really.
@dkekesi commented on GitHub (Nov 8, 2016):
The zip contains confidential information. Can you send me an email address where I can send the file to?
@dkekesi commented on GitHub (Apr 7, 2017):
Do you have any update on this? There are other files again with the same issue. If you can give me a mail address then I can send you the file.
@adamhathcock commented on GitHub (Apr 8, 2017):
I haven't looked into this at all and likely won't soon. Sorry.
I assume other things actually do open this zip? DotNetZip ought to have he same issue. You could try the built in zip stuff in .NET
@dkekesi commented on GitHub (Apr 8, 2017):
@dkekesi commented on GitHub (Jun 10, 2017):
It seems that version 0.17.1 can cope with the problematic file. I think this case can be closed.