This one is cute if you want to benchmark your computer: \showskips \starttext Hello! \stoptext Never stops generating pages Taco
Taco Hoekwater wrote:
This one is cute if you want to benchmark your computer:
\showskips \starttext Hello! \stoptext
Never stops generating pages
this is a known side effect. in the otr i reset the skips, but only when \showmakeup is used or when 'showcomposition = true' \def\dontshowcomposition {\ifshowingcomposition \dontshowfils \dontshowboxes \dontshowskips \dontshowpenalties \fi} so, the following works \showskips \showingcompositiontrue \starttext Hello! \stoptext (this show stuff has its limits and i gues you know why -) i'll add \showingcompositiontrue to the four \show... commands Hans
Hans Hagen wrote:
Patrick Gundlach wrote:
You mean that I can see how fast my computer finishes the endless loop? My Cray finishes those kind of loops in one week ;-)
long before that tex will reach its 64 K page limit -)
That's fixed, a while back. my pdfetex now quitted at [94729] [94730] [94731] [94732] [94733] [94734] [94735] [94736 ! TeX capacity exceeded, sorry [indirect objects table size=300000]. <output> {\shipout \box 255 \global \advance \pageno 1 \unhbox 255 } <to be read again> \end l.3 \bye ! ==> Fatal error occurred, the output PDF file is not finished! Transcript written on out.log. After a minute or two. Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
Patrick Gundlach wrote:
You mean that I can see how fast my computer finishes the endless loop? My Cray finishes those kind of loops in one week ;-)
long before that tex will reach its 64 K page limit -)
That's fixed, a while back. my pdfetex now quitted at
[94729] [94730] [94731] [94732] [94733] [94734] [94735] [94736 ! TeX capacity exceeded, sorry [indirect objects table size=300000]. <output> {\shipout \box 255 \global \advance \pageno 1 \unhbox 255 } <to be read again> \end l.3 \bye
! ==> Fatal error occurred, the output PDF file is not finished! Transcript written on out.log.
After a minute or two.
ah, so in practice it will quit earlier depending on other objects used (i'm not sure if for instance objects of included graphics use that piece of memory) Hans
Hans Hagen wrote:
That's fixed, a while back. my pdfetex now quitted at
[94729] [94730] [94731] [94732] [94733] [94734] [94735] [94736 ! TeX capacity exceeded, sorry [indirect objects table size=300000]. <output> {\shipout \box 255 \global \advance \pageno 1 \unhbox 255 } <to be read again> \end l.3 \bye
! ==> Fatal error occurred, the output PDF file is not finished! Transcript written on out.log.
After a minute or two.
ah, so in practice it will quit earlier depending on other objects used (i'm not sure if for instance objects of included graphics use that piece of memory)
This is mostly the required page objects. 3 objects are used per actual (totally empty) page: 13 0 obj << /Length 0 >> stream endstream endobj 12 0 obj << /Type /Page /Contents 13 0 R /Resources 11 0 R /MediaBox [0 0 595.2756 841.8898] /Parent 7 0 R >> endobj 11 0 obj << /ProcSet [ /PDF ] >> endobj It is a bit wasteful to keep those in the indirects objects table for ever and onwards, but I am not sure if it is doable to flush them right away. (CC ntg-pdftex) Greetings, Taco
Taco Hoekwater wrote:
Hans Hagen wrote:
That's fixed, a while back. my pdfetex now quitted at
[94729] [94730] [94731] [94732] [94733] [94734] [94735] [94736 ! TeX capacity exceeded, sorry [indirect objects table size=300000]. <output> {\shipout \box 255 \global \advance \pageno 1 \unhbox 255 } <to be read again> \end l.3 \bye
! ==> Fatal error occurred, the output PDF file is not finished! Transcript written on out.log.
After a minute or two.
ah, so in practice it will quit earlier depending on other objects used (i'm not sure if for instance objects of included graphics use that piece of memory)
This is mostly the required page objects. 3 objects are used per actual (totally empty) page:
13 0 obj << /Length 0 >> stream endstream endobj 12 0 obj << /Type /Page /Contents 13 0 R /Resources 11 0 R /MediaBox [0 0 595.2756 841.8898] /Parent 7 0 R >> endobj 11 0 obj << /ProcSet [ /PDF ] >> endobj
It is a bit wasteful to keep those in the indirects objects table for ever and onwards, but I am not sure if it is doable to flush them right away. (CC ntg-pdftex)
well, the procset is obsolete anyway, so that could save one object already Hans
On Thu, 17 Nov 2005, Taco Hoekwater wrote:
Hans Hagen wrote:
That's fixed, a while back. my pdfetex now quitted at
[94729] [94730] [94731] [94732] [94733] [94734] [94735] [94736 ! TeX capacity exceeded, sorry [indirect objects table size=300000].
after patch 386 one won't need to care for this mem anymore as it would grow dynamically up to size=10.000.000. Then such an error would happen only in really extreme cases. Regards, Hartmut
participants (4)
-
Hans Hagen -
Hartmut Henkel -
Patrick Gundlach -
Taco Hoekwater