Xelatex Capacity Issue?
up vote
0
down vote
favorite
I am compiling a file using my own *.cls file, which is a relatively minor modification of the Beamer class - mostly just to include a bunch of packages and extra commands I use. In this file, I include a large number of animations, using the animate package. Each frame in each animation is itself a PDF file, created by gnuplot. The final result is a 112 slide PDF output file.
Compiled on six-year old Apple laptop with XeLaTeX - result is that the document looks fine, except that not only all the animations, but even static images (with includegrapics) beyond a certain point are blank. There's just a big blank space where they should be. (The earlier ones look just fine.) The problem appears to be "compile time" rather than "run time", as viewing the file on a much more powerful Apple desktop computer results in the same problem.
Compile with XeLaTeX on the more powerful Apple desktop computer - result is a PDF file that functions exactly as it should, and the animations can also be viewed properly on the six-year old Apple laptop.
Compile with pdflatex on the six-year old Apple laptop - no problem. This is a potential solution, but I would like to do one or two small things in the file that require XeLaTeX (or maybe more precisely, I don't know how to do them with pdflatex).
The symptoms strike me like some kind of out-of-memory condition which is handled by producing a defective PDF (rather than an error message), but none of the limits at the end of the log file seem to have been violated. Under "xelatex --help", I also don't see any option to increase the memory.
Any thoughts on where I should be looking to try to hunt this one down?
Edited to add - the LaTeX installation on the old laptop is from 2016. (This is the one where XeLaTeX has problems, but pdflatex works just fine.) The installation on the more powerful computer, where both compilers work just fine, is from 2014.
graphics xetex animate memory
asked yesterday
RLK
505
|
show 2 more comments
up vote
0
down vote
favorite
I am compiling a file using my own *.cls file, which is a relatively minor modification of the Beamer class - mostly just to include a bunch of packages and extra commands I use. In this file, I include a large number of animations, using the animate package. Each frame in each animation is itself a PDF file, created by gnuplot. The final result is a 112 slide PDF output file.
Compiled on six-year old Apple laptop with XeLaTeX - result is that the document looks fine, except that not only all the animations, but even static images (with includegrapics) beyond a certain point are blank. There's just a big blank space where they should be. (The earlier ones look just fine.) The problem appears to be "compile time" rather than "run time", as viewing the file on a much more powerful Apple desktop computer results in the same problem.
Compile with XeLaTeX on the more powerful Apple desktop computer - result is a PDF file that functions exactly as it should, and the animations can also be viewed properly on the six-year old Apple laptop.
Compile with pdflatex on the six-year old Apple laptop - no problem. This is a potential solution, but I would like to do one or two small things in the file that require XeLaTeX (or maybe more precisely, I don't know how to do them with pdflatex).
The symptoms strike me like some kind of out-of-memory condition which is handled by producing a defective PDF (rather than an error message), but none of the limits at the end of the log file seem to have been violated. Under "xelatex --help", I also don't see any option to increase the memory.
Any thoughts on where I should be looking to try to hunt this one down?
Edited to add - the LaTeX installation on the old laptop is from 2016. (This is the one where XeLaTeX has problems, but pdflatex works just fine.) The installation on the more powerful computer, where both compilers work just fine, is from 2014.
graphics xetex animate memory
asked yesterday
RLK
505
No, first line of output of "xelatex --version" on the laptop. XeTeX 3.14159265-2.6-0.99996 (TeX Live 2016) In fact, this is newer than the version on the more powerful desktop, which produces correct output.
– RLK
yesterday
Also, pdflatex on the same computer seems to process the file without any problems.
– RLK
yesterday
I should also add - my temporary solution to this (before I realised that pdflatex would work, and xelatex on the other computer would work) was to split the source document into several smaller docs, so that none of them contained too many animations. That worked.
– RLK
yesterday
1
Runxelatex --no-pdf fileand thenxdvipdfmx -vv file.xdvon a command line. Perhaps this gives more info.
– Ulrike Fischer
yesterday
there were some important fixes to image handling in xdvipdfmx as i recall so it may be failing there rather than in xelatex.
– David Carlisle
yesterday
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am compiling a file using my own *.cls file, which is a relatively minor modification of the Beamer class - mostly just to include a bunch of packages and extra commands I use. In this file, I include a large number of animations, using the animate package. Each frame in each animation is itself a PDF file, created by gnuplot. The final result is a 112 slide PDF output file.
Compiled on six-year old Apple laptop with XeLaTeX - result is that the document looks fine, except that not only all the animations, but even static images (with includegrapics) beyond a certain point are blank. There's just a big blank space where they should be. (The earlier ones look just fine.) The problem appears to be "compile time" rather than "run time", as viewing the file on a much more powerful Apple desktop computer results in the same problem.
Compile with XeLaTeX on the more powerful Apple desktop computer - result is a PDF file that functions exactly as it should, and the animations can also be viewed properly on the six-year old Apple laptop.
Compile with pdflatex on the six-year old Apple laptop - no problem. This is a potential solution, but I would like to do one or two small things in the file that require XeLaTeX (or maybe more precisely, I don't know how to do them with pdflatex).
The symptoms strike me like some kind of out-of-memory condition which is handled by producing a defective PDF (rather than an error message), but none of the limits at the end of the log file seem to have been violated. Under "xelatex --help", I also don't see any option to increase the memory.
Any thoughts on where I should be looking to try to hunt this one down?
Edited to add - the LaTeX installation on the old laptop is from 2016. (This is the one where XeLaTeX has problems, but pdflatex works just fine.) The installation on the more powerful computer, where both compilers work just fine, is from 2014.
graphics xetex animate memory
asked yesterday
RLK
505
I am compiling a file using my own *.cls file, which is a relatively minor modification of the Beamer class - mostly just to include a bunch of packages and extra commands I use. In this file, I include a large number of animations, using the animate package. Each frame in each animation is itself a PDF file, created by gnuplot. The final result is a 112 slide PDF output file.
Compiled on six-year old Apple laptop with XeLaTeX - result is that the document looks fine, except that not only all the animations, but even static images (with includegrapics) beyond a certain point are blank. There's just a big blank space where they should be. (The earlier ones look just fine.) The problem appears to be "compile time" rather than "run time", as viewing the file on a much more powerful Apple desktop computer results in the same problem.
Compile with XeLaTeX on the more powerful Apple desktop computer - result is a PDF file that functions exactly as it should, and the animations can also be viewed properly on the six-year old Apple laptop.
Compile with pdflatex on the six-year old Apple laptop - no problem. This is a potential solution, but I would like to do one or two small things in the file that require XeLaTeX (or maybe more precisely, I don't know how to do them with pdflatex).
The symptoms strike me like some kind of out-of-memory condition which is handled by producing a defective PDF (rather than an error message), but none of the limits at the end of the log file seem to have been violated. Under "xelatex --help", I also don't see any option to increase the memory.
Any thoughts on where I should be looking to try to hunt this one down?
Edited to add - the LaTeX installation on the old laptop is from 2016. (This is the one where XeLaTeX has problems, but pdflatex works just fine.) The installation on the more powerful computer, where both compilers work just fine, is from 2014.
graphics xetex animate memory
graphics xetex animate memory
asked yesterday
RLK
505
asked yesterday
RLK
505
edited yesterday
asked yesterday
RLK
505
asked yesterday
RLK
505
asked yesterday
RLK
505
505
No, first line of output of "xelatex --version" on the laptop. XeTeX 3.14159265-2.6-0.99996 (TeX Live 2016) In fact, this is newer than the version on the more powerful desktop, which produces correct output.
– RLK
yesterday
Also, pdflatex on the same computer seems to process the file without any problems.
– RLK
yesterday
I should also add - my temporary solution to this (before I realised that pdflatex would work, and xelatex on the other computer would work) was to split the source document into several smaller docs, so that none of them contained too many animations. That worked.
– RLK
yesterday
1
Runxelatex --no-pdf fileand thenxdvipdfmx -vv file.xdvon a command line. Perhaps this gives more info.
– Ulrike Fischer
yesterday
there were some important fixes to image handling in xdvipdfmx as i recall so it may be failing there rather than in xelatex.
– David Carlisle
yesterday
|
show 2 more comments
No, first line of output of "xelatex --version" on the laptop. XeTeX 3.14159265-2.6-0.99996 (TeX Live 2016) In fact, this is newer than the version on the more powerful desktop, which produces correct output.
– RLK
yesterday
Also, pdflatex on the same computer seems to process the file without any problems.
– RLK
yesterday
I should also add - my temporary solution to this (before I realised that pdflatex would work, and xelatex on the other computer would work) was to split the source document into several smaller docs, so that none of them contained too many animations. That worked.
– RLK
yesterday
1
Runxelatex --no-pdf fileand thenxdvipdfmx -vv file.xdvon a command line. Perhaps this gives more info.
– Ulrike Fischer
yesterday
there were some important fixes to image handling in xdvipdfmx as i recall so it may be failing there rather than in xelatex.
– David Carlisle
yesterday
No, first line of output of "xelatex --version" on the laptop. XeTeX 3.14159265-2.6-0.99996 (TeX Live 2016) In fact, this is newer than the version on the more powerful desktop, which produces correct output.
– RLK
yesterday
No, first line of output of "xelatex --version" on the laptop. XeTeX 3.14159265-2.6-0.99996 (TeX Live 2016) In fact, this is newer than the version on the more powerful desktop, which produces correct output.
– RLK
yesterday
Also, pdflatex on the same computer seems to process the file without any problems.
– RLK
yesterday
Also, pdflatex on the same computer seems to process the file without any problems.
– RLK
yesterday
I should also add - my temporary solution to this (before I realised that pdflatex would work, and xelatex on the other computer would work) was to split the source document into several smaller docs, so that none of them contained too many animations. That worked.
– RLK
yesterday
I should also add - my temporary solution to this (before I realised that pdflatex would work, and xelatex on the other computer would work) was to split the source document into several smaller docs, so that none of them contained too many animations. That worked.
– RLK
yesterday
1
1
Run
xelatex --no-pdf file and then xdvipdfmx -vv file.xdv on a command line. Perhaps this gives more info.– Ulrike Fischer
yesterday
Run
xelatex --no-pdf file and then xdvipdfmx -vv file.xdv on a command line. Perhaps this gives more info.– Ulrike Fischer
yesterday
there were some important fixes to image handling in xdvipdfmx as i recall so it may be failing there rather than in xelatex.
– David Carlisle
yesterday
there were some important fixes to image handling in xdvipdfmx as i recall so it may be failing there rather than in xelatex.
– David Carlisle
yesterday
|
show 2 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f461095%2fxelatex-capacity-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
No, first line of output of "xelatex --version" on the laptop. XeTeX 3.14159265-2.6-0.99996 (TeX Live 2016) In fact, this is newer than the version on the more powerful desktop, which produces correct output.
– RLK
yesterday
Also, pdflatex on the same computer seems to process the file without any problems.
– RLK
yesterday
I should also add - my temporary solution to this (before I realised that pdflatex would work, and xelatex on the other computer would work) was to split the source document into several smaller docs, so that none of them contained too many animations. That worked.
– RLK
yesterday
1
Run
xelatex --no-pdf fileand thenxdvipdfmx -vv file.xdvon a command line. Perhaps this gives more info.– Ulrike Fischer
yesterday
there were some important fixes to image handling in xdvipdfmx as i recall so it may be failing there rather than in xelatex.
– David Carlisle
yesterday