Red Hat Bugzilla – Bug 91683
gs (invoked from ggv) eats CPU and RAM, triggers swap storm
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030509
Description of problem:
When I attempt to view this PDF using ggv, my laptop became completely locked up
for about a minute as a swap storm ensues in the background. From a remote ssh
terminal it appeared that a "gs" process using 100% CPU, ate 512MB RAM and was
causing heavy swapping. Eventually about a minute later memory freed up and the
system became responsive again. GGV window opened displaying the PDF file.
When you first run ggv, a gs process grows beyond 500MB in memory, using 100%
CPU. Eventually this subsides and uses 100% CPU with very little RAM usage.
Then finally the ggv window opens, and for 20 seconds it draws the PDF in the
window from the bottom up. (1GHz Athlon)
xpdf and kghostview do not take anywhere near this amount of RAM or CPU when
viewing this document.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download that PDF.
2. Read it with ggv.
Should be quick like xpdf or kghostview.
To reproduce the problem outside ggv:
gs -q -dNOPAUSE -dBATCH -dSAFER -dQUIET -sDEVICE=pswrite -sOutputFile=/dev/null
Another PDF which exhibits this problem.
Still broken in latest post-Severn rawhide ghostscript-7.07-10
Both test cases seem to work in ggv with FC1 + all updates.