bib module and pdftex 1.40.7: Virtual memory exhausted using MiKTeX-2.7
Consider the trivial test file: ------------------------------------- % example from: http://wiki.contextgarden.net/Bibliography % Format using: % $ texexec --once t-cont % $ bibtex t-cont % $ texexec t-cont \usemodule[bib] \usemodule[bibltx] \setupbibtex[database=xampl] \starttext As \cite[article-full] already indicated, bibtex is a \LaTeX-centric program. \completepublications \stoptext ------------------------------------- Following instructions: -------------------------------------
texexec --once bibdemo TeXExec | processing document 'bibdemo' TeXExec | no ctx file found TeXExec | tex processing method: context TeXExec | writing option file bibdemo.top TeXExec | using randomseed 595 TeXExec | tex engine: pdftex TeXExec | tex format: cont-en This is pdfTeX, Version 3.141592-1.40.7 (MiKTeX 2.7) entering extended mode (bibdemo.tex
ConTeXt ver: 2008.01.28 21:28 MKII fmt: 2008.2.18 int: english/english
[....]
Output written on bibdemo.pdf (2 pages, 42919 bytes).
Transcript written on bibdemo.log.
pdftex: Virtual memory exhausted while trying to reserve 8 bytes for table
???.
TeXExec | runtime: 2.828
-------------------------------------------
I don't see this on my linux machines with older versions of ConTeXt and
pdftex.
Simple LaTeX documents and ConTeXt documents that don't use the bib module
don't give the error, so it looks like the bib module reveals a bug in
pdftex-1.40.n,
for some n larger than 3.
--
George N. White III
George N. White III wrote:
Consider the trivial test file:
------------------------------------- % example from: http://wiki.contextgarden.net/Bibliography % Format using: % $ texexec --once t-cont % $ bibtex t-cont % $ texexec t-cont \usemodule[bib] \usemodule[bibltx] \setupbibtex[database=xampl] \starttext As \cite[article-full] already indicated, bibtex is a \LaTeX-centric program. \completepublications \stoptext
This is pdfTeX, Version 3.141592-1.40.7 (MiKTeX 2.7)
here i run This is pdfTeX, Version 3.141592-1.40.5 (Web2C 7.5.6) and that one does not crash; then i upated to This is pdfTeX, Version 3.141592-1.50.0-alpha-20080214 (Web2C 7.5.6) which also runs ok. maybe it's a miktex issue? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Feb 19, 2008, at 9:41 PM, Hans Hagen wrote:
here i run
This is pdfTeX, Version 3.141592-1.40.5 (Web2C 7.5.6)
and that one does not crash; then i upated to
This is pdfTeX, Version 3.141592-1.50.0-alpha-20080214 (Web2C 7.5.6)
which also runs ok. maybe it's a miktex issue?
Hans
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. Thomas
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 ?
-- luigi it's new . it's powerful . it's luatex . http://www.luatex.org
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
Thomas A. Schmitz wrote:
! TeX capacity exceeded, sorry [PDF object stream buffer=5].
that looks quite small to me Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Feb 27, 2008, at 10:52 AM, Hans Hagen wrote:
that looks quite small to me
Hans
Question is: where does this value come from? Since it only occurs in 1.40.7, it must be some default value set during compilation of pdftex, I assume? Thomas
Thomas A. Schmitz wrote:
On Feb 27, 2008, at 10:52 AM, Hans Hagen wrote:
that looks quite small to me
Hans
Question is: where does this value come from? Since it only occurs in 1.40.7, it must be some default value set during compilation of pdftex, I assume?
Probably pdftex's intention is more like 300.000, but there is an alignment shift because of byte order differences. (300000>>16 == 5). I suspect there will be a 1.40.8 Best wishes, Taco
Thomas A. Schmitz wrote:
On Feb 27, 2008, at 10:52 AM, Hans Hagen wrote:
that looks quite small to me
Hans
Question is: where does this value come from? Since it only occurs in 1.40.7, it must be some default value set during compilation of pdftex, I assume?
it used to be a configurable setting, but now pdf mem is fully dynamic anyhow, it's just a bug and there's nothing you can do about it -) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
George N. White III wrote:
Output written on bibdemo.pdf (2 pages, 42919 bytes). Transcript written on bibdemo.log.
pdftex: Virtual memory exhausted while trying to reserve 8 bytes for table ???.
It seems the error happens at the moment (or just before) pdftex is exited, which is an odd moment for an 'out of memory' type of problem. It looks to me like the error message comes from the operating system itself (it certainly does not look like a normal pdftex error, and I had not heard of it until now). It could be a problem that exists only in the miktex 2.7 version of pdftex, but there could also be an underlying problem in pdftex that for some reason only surfaces in miktex, has to say for sure. In any case, I cannot reproduce this on linux, and as far as I know none of the core pdftex developers use miktex, so you may have to ask on the miktex mailinglist instead. Best wishes, Taco
On Feb 19, 2008 10:53 PM, Taco Hoekwater wrote:
George N. White III wrote:
Output written on bibdemo.pdf (2 pages, 42919 bytes). Transcript written on bibdemo.log.
pdftex: Virtual memory exhausted while trying to reserve 8 bytes for table ???.
It seems the error happens at the moment (or just before) pdftex is exited, which is an odd moment for an 'out of memory' type of problem. It looks to me like the error message comes from the operating system itself (it certainly does not look like a normal pdftex error, and I had not heard of it until now).
It could be a problem that exists only in the miktex 2.7 version of pdftex, but there could also be an underlying problem in pdftex that for some reason only surfaces in miktex, has to say for sure. In any case, I cannot reproduce this on linux, and as far as I know none of the core pdftex developers use miktex, so you may have to ask on the miktex mailinglist instead.
Rather MikTeX developer directly or enter it to the bug tracker - MikTeX mailing list is nearly "dead" in comparison to this one. Mojca
On Tue, Feb 19, 2008 at 8:01 PM, George N. White III
Consider the trivial test file:
------------------------------------- % example from: http://wiki.contextgarden.net/Bibliography % Format using: % $ texexec --once t-cont % $ bibtex t-cont % $ texexec t-cont \usemodule[bib] \usemodule[bibltx] \setupbibtex[database=xampl] \starttext As \cite[article-full] already indicated, bibtex is a \LaTeX-centric program. \completepublications \stoptext -------------------------------------
Following instructions: -------------------------------------
texexec --once bibdemo TeXExec | processing document 'bibdemo' TeXExec | no ctx file found TeXExec | tex processing method: context TeXExec | writing option file bibdemo.top TeXExec | using randomseed 595 TeXExec | tex engine: pdftex TeXExec | tex format: cont-en This is pdfTeX, Version 3.141592-1.40.7 (MiKTeX 2.7) entering extended mode (bibdemo.tex
ConTeXt ver: 2008.01.28 21:28 MKII fmt: 2008.2.18 int: english/english [....]
Output written on bibdemo.pdf (2 pages, 42919 bytes). Transcript written on bibdemo.log.
pdftex: Virtual memory exhausted while trying to reserve 8 bytes for table ???. TeXExec | runtime: 2.828 -------------------------------------------
I don't see this on my linux machines with older versions of ConTeXt and pdftex. Simple LaTeX documents and ConTeXt documents that don't use the bib module don't give the error, so it looks like the bib module reveals a bug in pdftex-1.40.n, for some n larger than 3. No problems here in a linux box with
ConTeXt ver: 2007.04.17 pdfTeXk, Version 3.141592-1.40.7 ConTeXt ver: 2008.01.28 21:28 MKII fmt: 2008.2.20 int: english/english pdfTeXk, Version 3.141592-1.40.7 ConTeXt ver: 2008.01.28 21:28 MKIV fmt: 2008.2.20 int: english/english This is LuaTeX, Version snapshot-0.22.0-2008021609 This is build 915, created on 20071128T092554Z Compiled with libpng 1.2.15; using libpng 1.2.15 Compiled with zlib 1.2.3; using zlib 1.2.3 Compiled with xpdf version 3.01 -- luigi it's new . it's powerful . it's luatex . http://www.luatex.org
George N. White III wrote:
Consider the trivial test file:
------------------------------------- % example from: http://wiki.contextgarden.net/Bibliography % Format using: % $ texexec --once t-cont % $ bibtex t-cont % $ texexec t-cont \usemodule[bib] \usemodule[bibltx] \setupbibtex[database=xampl] \starttext As \cite[article-full] already indicated, bibtex is a \LaTeX-centric program. \completepublications \stoptext -------------------------------------
Following instructions: -------------------------------------
texexec --once bibdemo TeXExec | processing document 'bibdemo' TeXExec | no ctx file found TeXExec | tex processing method: context TeXExec | writing option file bibdemo.top TeXExec | using randomseed 595 TeXExec | tex engine: pdftex TeXExec | tex format: cont-en This is pdfTeX, Version 3.141592-1.40.7 (MiKTeX 2.7) entering extended mode (bibdemo.tex
ConTeXt ver: 2008.01.28 21:28 MKII fmt: 2008.2.18 int: english/english [....]
Output written on bibdemo.pdf (2 pages, 42919 bytes). Transcript written on bibdemo.log.
pdftex: Virtual memory exhausted while trying to reserve 8 bytes for table ???.
MiKTeX talks wild here. The correct message should be: "The heap is corrupted." The problem shows up when the fontinfo array is freed (at the end of the pdfTeX run). IIRC, Web2C never frees any tables, i.e., you will never see this problem in TeX live.
participants (8)
-
Christian Schenk -
George N. White III -
Hans Hagen -
luigi scarso -
Martin Schröder -
Mojca Miklavec -
Taco Hoekwater -
Thomas A. Schmitz