[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: printing problems because of memory consumption of gs
From: |
Daniel J Sebald |
Subject: |
Re: printing problems because of memory consumption of gs |
Date: |
Sun, 04 Jan 2015 16:07:32 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 01/04/2015 09:40 AM, Torsten wrote:
With a recent build from the gui-release branch I encounter the problem
that printing a figure (gnuplot) starts a gs-process that consumes up to
2 GB of memory. This makes it nearly impossible to build the docs on a
computer with only 2 GB. Plotting directly in gnuplot with an eps-, pdf-
or png-terminal is no problem. Is anyone else seeing this issue?
Best regards,
Torsten
I ran across a compilation bug (and created a small changeset):
https://savannah.gnu.org/bugs/index.php?43932
After fixing that I don't see such an issue that you describe, but I'm
not sure what command you are using. I simply switched to the gnuplot
graphics toolkit and did a simple plot and print:
graphics_toolkit gnuplot
plot([1:500])
print
and see no large ghostscript process appearing.
The problems I'm having stem from failure to build documentation, such
as the following example:
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed:
(connection->initialization_error == NULL)
octave exited with signal 6
../../run-octave -f -q -H -p
/home/sebald/octave/octave/octave/doc/interpreter --eval "splineimages
('splinefit1', 'pdf');"
which happens for about 100 examples. This splines example takes a
really long time to run, btw. Following that I have issues building the
tex files because of missing figures.
Then after installation I see:
help print
error: unable to open /usr/local/share/octave/3.9.0+/etc/macros.texi for
reading
error: called from:
error: /usr/local/share/octave/3.9.0+/m/help/__makeinfo__.m at line
103, column 5
error: /usr/local/share/octave/3.9.0+/m/help/help.m at line 99, column 22
I'll investigate this when I can, probably something missing on my system.
Dan