Comment 5 for bug 1846464

Revision history for this message
Brian Foster (blfoster) wrote :

Now confirmed, using the PDF kindly attached in #3.
There actually is some output, the output file `Plan.pdf' has been created
and is --- slowly --- relentlessly growing. It grew to c.68MiB by letting
pdfposter(1) run for 10mins (real-time) solid, fully occupying one of my
cores (100% of one CPU). However, the memory usage did_not_ increase.
When I finally gave up and ^C'ed, I got:

$ pdfposter --scale=4 Micro-Magic_Plan_2016_V2.pdf Plan.pdf
^CTraceback (most recent call last):
  File "/usr/bin/pdfposter", line 9, in <module>
    load_entry_point('pdftools.pdfposter==0.6.0', 'console_scripts', 'pdfposter')()
  File "/usr/share/pdfposter/pdftools/pdfposter/cmd.py", line 129, in run
    main(opts, *args)
  File "/usr/share/pdfposter/pdftools/pdfposter/__init__.py", line 340, in main
    outpdf.write(open(outfilename, 'wb'))
  File "/usr/lib/python2.7/dist-packages/PyPDF2/pdf.py", line 501, in write
    obj.writeToStream(stream, key)
  File "/usr/lib/python2.7/dist-packages/PyPDF2/generic.py", line 785, in writeToStream
    self[NameObject("/Length")] = NumberObject(len(self._data))
  File "/usr/lib/python2.7/dist-packages/PyPDF2/pdf.py", line 2771, in _getData
    newdata.write(b_(operator))
KeyboardInterrupt
$

Unsurprisingly, the output `Plan.pdf' is incomplete and/or corrupt.

I do_not_ know whether it would complete if I had the patience and disc space
to let in churn away.