Bug 57683 - kghostview runs with 99% cpu usage
kghostview runs with 99% cpu usage
Product: Red Hat Linux
Classification: Retired
Component: kdegraphics (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Depends On:
  Show dependency treegraph
Reported: 2001-12-18 16:30 EST by Markus
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-20 07:50:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Markus 2001-12-18 16:30:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6+) Gecko/20011212

Description of problem:
kghostview runs with every pdf and ps-file with 99% cpu-usage. the new
kde2.2.2 has the same problem. 

95.9 : markus   : 14808 : kghostview file:/home/markus/l2kurz.pdf -caption
PS/PDF Viewer -icon kghostview -min 
0.2 : markus   : 14811 : gs -sDEVICE=x11 -dTextAlphaBits=4
-dGraphicsAlphaBits=2 -dMaxBitmap=10000000 -dNOPLA

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.open a pdf or postscript file

Additional info:

since kde 2.2
Comment 1 Alexei Podtelezhnikov 2001-12-18 18:27:51 EST
I suspect that you are an upgrading freak, like i am. ... just judging by you 
version of mozilla.
Do you use qt-2.3.2? If so, do you see the problem with 2.3.1?
Downgrading might help. Report back
Comment 2 Markus 2001-12-20 07:50:12 EST
i now use qt2.3.1-2.3.2 was *really* buggy...

i had the problem with roswell and wrote to the kde bug tracking system-but
nothing happened. 

Comment 3 Bernhard Rosenkraenzer 2002-01-17 09:53:38 EST
Fixed in the current tree
Comment 4 Alexei Podtelezhnikov 2002-01-17 20:43:54 EST
The fix is painfully simple:
Settings/Configure KGhostView/Ghostscript and click "Configure..."

Note You need to log in before you can comment on or make changes to this bug.