Writing a long docx file

Open
#456 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

Start at DocX.Save(String password) and trace the packaging stream calls shown in the stack trace while reproducing the failure with a large document. The issue provides no repository file, test, or acceptance criterion, so completion cannot be defined from the report alone.

Written by the indexing model from the issue text.

Description

Hi, When I use DocX to write a large file, during the Save, it produces error, stream is too long.
Do you have any hint for this error?
Thank you

在 System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count) 在 MS.Internal.IO.Packaging.SparseMemoryStream.CopyMemoryBlocksToStream(Stream targetStream) 在 MS.Internal.IO.Packaging.SparseMemoryStream.WriteToStream(Stream stream) 在 MS.Internal.IO.Zip.ZipIOFileItemStream.Save() 在 MS.Internal.IO.Zip.ZipIOLocalFileBlock.Save() 在 MS.Internal.IO.Zip.ZipIOBlockManager.SaveContainer(Boolean closingFlag) 在 MS.Internal.IO.Zip.ZipIOBlockManager.SaveStream(ZipIOLocalFileBlock blockRequestingFlush, Boolean closingFlag) 在 MS.Internal.IO.Packaging.CompressEmulationStream.Flush() 在 MS.Internal.IO.Packaging.CompressStream.Flush() 在 Xceed.Document.NET.PackagePartStream.Flush() 在 System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) 在 System.Xml.XmlEncodedRawTextWriter.Flush() 在 System.Xml.XmlWellFormedWriter.Close() 在 System.Xml.XmlWriter.Dispose(Boolean disposing) 在 System.Xml.Linq.XDocument.Save(TextWriter textWriter, SaveOptions options) 在 Xceed.Words.NET.DocX.Save(String password) 在

Dominant language
C#
Stars
1.9k
Forks
483
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xceedsoftware/DocX

All issues in xceedsoftware/DocX

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.