From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/461 Path: main.gmane.org!not-for-mail From: Matthew Baker Newsgroups: gmane.comp.tex.context Subject: Linux Acroread memory link with Context Date: Sat, 29 May 1999 17:28:41 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: Reply-To: Matthew.Baker@gmd.de NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1035391319 24238 80.91.224.250 (23 Oct 2002 16:41:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:41:59 +0000 (UTC) Original-To: Context List Xref: main.gmane.org gmane.comp.tex.context:461 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:461 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