|
|
Rank: Advanced Member
Groups: Member
Joined: 1/22/2014
Posts: 38
|
Have files which I can open and save without issue, but whenever they are part of a merge causes PdfDocument.Merge to crash hard with this stack trace:
at EO.Pdf.PdfGoToAction.a()
at EO.Internal.are.a()
at EO.Internal.n7.a()
at EO.Pdf.PdfPage.a()
at EO.Pdf.PdfPageCollection.a(Boolean A_0)
at EO.Internal.hm.a()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Save(Stream stream)
Is there anything that can be done to prevent this or find out what/why?
Thank you in advance.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
What version of EO.Pdf do you use?
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/22/2014
Posts: 38
|
17.2.14.0
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi, This might be an issue on our end. Can you send us the files that you are trying to merge so that we can take a look? See here for more information on how to send test files to us: https://www.essentialobjects.com/forum/test_project.aspxThanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 1/22/2014
Posts: 38
|
Unfortunately we cannot share the data due to agreements. I can say I was able to work around the issue by merging through another third party library, but ideally this could be somehow stack traced or something without data to where you can get an idea of the issue.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
As a general rule, we will not shoot in the dark without an actual test file to verify whether it indeed solves the problem or not. For an issue to be clearly resolved, we must have a way to reproduce it, find out exactly what caused it, fix it and verify it. These are not possible without the file in question. We can get some ideas about what might have gone wrong based on the stack trace, but to be absolutely sure about what went wrong, we need the file. For a product to be robust, we need to be absolutely sure instead of just changing code based on what might have gone wrong. We are not interested in the actual contents of your file --- we just need the file to verify the issue and fix. We are open to sign NDA with you if that's an option for you.
|
|