From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bib module and pdftex 1.40.7: Virtual memory exhausted using MiKTeX-2.7
Date: Wed, 27 Feb 2008 10:26:46 +0100 [thread overview]
Message-ID: <57494D55-1617-4E27-A990-E43855E0BD33@uni-bonn.de> (raw)
In-Reply-To: <fe8d59da0802200105t755f018di58203199127b0dc2@mail.gmail.com>
On Feb 20, 2008, at 10:05 AM, luigi scarso wrote:
>> Just the other day, I encountered a mysterious error which may or may
>> not be related. I upgraded to pdftex 1.40.7 on all my boxes. This was
>> smooth on my intel-macs (OS X 10.5.2). On my powerpc-mac, I got a
>> "TeX
>> capacity exceeded!" error with 1.40.7 for a file that compiled fine
>> with 1.40.5. I tried several times: all I did was dropping the pdftex
>> binary and pdftex.pool in place, rebuilding th format and compiling
>> the file. Compilation was smooth with 1.40.5 and consistently failed
>> with 1.40.7 (which I compiled and recompiled without any special
>> flags). I haven't pursued the matter for the moment and just went
>> back
>> to 1.40.5, but I'm wondering if these problems are related.
> Do you have a test file ?
>
Sorry, it took me a while because this is the computer in my office,
from which I;ve been away for a while. I think I nailed it down: if I
try to include a pdf image into a ConTeXt document
\starttext
\externalfigure[Logo][width=56mm,height=20mm]
\stoptext
(with any pdf file) I get this error:
<./Logo.pdf
! TeX capacity exceeded, sorry [PDF object stream buffer=5].
\dogetTPDfiguresize ...geBox {\@@DriverImageFile }
\xdef
\PDFimagereference {...
\doanalyzefiguredimensionsinternal ...tfiguresize
\setanalyzedfiguredimensio...
<argument> ...}\doanalyzefiguredimensionsinternal
\doanalyzefiguredimensions...
\firstoftwoarguments #1#2->#1
\dododoanalyzeunknownfiguretype ...guredimensions
\fi
\next2 ...dododoanalyzeunknownfiguretype {pdf}{#1}
\doprocesscommaitem
...
l.4
! ==> Fatal error occurred, no output PDF file produced!
The pdf file is OK; this error only occurs with pdftex 1.40.7 on
powerpc (OS X, 10.5.2). The same file compiles fine with
luatex on powerpc and intel
pdftex 1.40.5 on powerpc and intel
pdftex 1.40.7 on OS X intel
All best
Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-02-27 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 19:01 George N. White III
2008-02-19 20:41 ` Hans Hagen
2008-02-20 8:57 ` Thomas A. Schmitz
2008-02-20 9:05 ` luigi scarso
2008-02-27 9:26 ` Thomas A. Schmitz [this message]
2008-02-27 9:52 ` Hans Hagen
2008-02-27 9:58 ` Thomas A. Schmitz
2008-02-27 10:15 ` Taco Hoekwater
2008-02-27 11:23 ` Hans Hagen
2008-02-27 12:05 ` Martin Schröder
2008-02-27 13:50 ` Thomas A. Schmitz
2008-02-19 21:53 ` Taco Hoekwater
2008-02-19 22:14 ` Mojca Miklavec
2008-02-19 23:44 ` luigi scarso
2008-02-20 9:39 ` Christian Schenk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57494D55-1617-4E27-A990-E43855E0BD33@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).