From: Matthew Baker <mbaker@zeus.gmd.de>
Subject: Linux Acroread memory link with Context
Date: Sat, 29 May 1999 17:28:41 +0200 [thread overview]
Message-ID: <Pine.SGI.4.04.9905291708110.156134-100000@sono> (raw)
Hi,
Last week I posted a message about Linux Acroread's memory usage growing
as I browse through an image-intensive document I'm working on. I've
played with this a bit more and have found the following:
1. Even if I have a document with a small number of images, flipping back
and forth between pages containing big images eventually takes up more
and more swap space. So it seems images are not being deallocated
after use, or something along those lines.
2. Converting the document to PostScript with Acrobat (Linux version) then
converting the PostScript file back to PDF with Distiller (3.0, Win)
elliminates this problem, ie the resulting file doesn't result in the
memory leak when viewed under Linux.
3. Acroread 3.0 and 4.0 beta both exhibit this problem.
4. I don't have any problems under Windows. I haven't tried other Unix
platforms yet.
So, to me it seems that it is either a Context or pdftex bug since the
same images converted to PDF with Distiller don't cause problems. Or if
not a bug, something which triggers a bug in Linux Acroread that Distiller
PDF files don't trigger.
For a test document, all I'm using is several pages of \startcombination
... \stopcombination with 9 images in each. Images are 256x384 pixels
each, so they are not in any way unreasonably big. I monitor memory usage
by watching swap space in xosview.
Any ideas why this might happen? Next step for me is to try something
with plain pdftex and includegraphics commands to see if that causes the
same problem.
Cheers,
Matthew
--
Dr. Matthew Baker matthew.baker@gmd.de
GMD - FIT.MMK http://fit.gmd.de/hci/pages/matthew.baker.html
next reply other threads:[~1999-05-29 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-29 15:28 Matthew Baker [this message]
1999-05-30 23:33 ` Hans Hagen
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=Pine.SGI.4.04.9905291708110.156134-100000@sono \
--to=mbaker@zeus.gmd.de \
--cc=Matthew.Baker@gmd.de \
/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).