Unexpected data in xref table about pdfmerger

[myokyawhtun]

Can you refer to this comment.

#7 (comment)

Sorry for sending to you late as I'm not longer active in improving this PDFMerger.

[toonvandenbos]

Thank you for your response.

The PDFs I want to merge are generated by dompdf. When I try to download them separetly, everything looks fine (and after checking them, they don't seem to be corrupt).

Maybe it's the PDF version of the generated files. I'll have a look.

[mdunbavan]

Hi @Nyratas did you ever resolve this issue? I've just come across this now

[toonvandenbos]

@mdunbavan I don't remember how this story ended... But I know for sure we didn't find a solution for this specific issue. I think there were some process-changes later on and we didn't have to merge PDFs anymore. So no, can't help, sorry !

[mdunbavan]

@Nyratas when you say merging what do you mean?

[toonvandenbos]

@mdunbavan We generated two PDF files (they had different formats and stuff) and wanted to merge them in order to make a single downloadable PDF (one file containing the two previously generated files in a specific order).

[mdunbavan]

Mine is just a simple 1 pdf but on my local dev version it all works well as soon as I put this on staging it throws the error above. I thought it was an issue with the pdf created but thats not it all I can say is that it could be the version of the package or the php?

[toonvandenbos]

@mdunbavan We had the exact same environment locally and on staging, but still didn't work on staging server. I really don't know where this issue's coming from since we had same versions locked into a composer.lock...

[myokyawhtun]

@Nyratas isn't because of server specs especially RAM or memory allocated for PHP processing? I've had the problem before. Merging so many PDFs in my local machine without problem and didn't work on company's staging server. Later turn out because of PHP memory issue since staging server just set 16 M or something like that. @mdunbavan