You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
System.NotSupportedException when zipping more than ~4.2 gb of data to a stream that doesn't support seeking #164
You have to zip up enough data so that when the stream is writing the end of the central directory the function ZipHelperStream.WriteZip64EndOfCentralDirectory will be called. The first thing this does is call stream_.Position which immediately fails if the stream being written to doesn't support seeking and therefore doesn't support position. MSDN describes the relationship between the stream position property and the CanSeek property.
Expected behavior
Ideally, the stream's position would not be needed at all. Instead I think this should be tracked like the sizeEntries or startOfCentralDirectory is already being tracked by SharpZipLib.
Actual behavior
Since the underlying stream does not support seeking the stream's position property throws a System.NotSupportedException which then bubbles up.
Version of SharpZipLib
0.86.0.518
Obtained from (place an x between the brackets for all that apply)
changed the title [-]System.NotSupportedException when zipping more than ~4.2 gb of data to a stream doesn't support seeking[/-][+]System.NotSupportedException when zipping more than ~4.2 gb of data to a stream that doesn't support seeking[/+]on Jan 19, 2017
Activity
[-]System.NotSupportedException when zipping more than ~4.2 gb of data to a stream doesn't support seeking[/-][+]System.NotSupportedException when zipping more than ~4.2 gb of data to a stream that doesn't support seeking[/+]insylogo commentedon Apr 25, 2018
Here's a PR that addresses this issue: #226
Merge pull request #226 from insylogo/master