Bug 64614

Summary:	Very poor performance with antialiasing in gv
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <winstonc>
Component:	gv	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-05-08 19:43:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2002-05-08 17:08:14 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408

Description of problem:
gv is very slow rendering documents with antialiasing turned on.  Performance in
older versions (RH 7.2) was much faster.

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


How reproducible:
Always

Steps to Reproduce:
1. Open a postscript document with gv.
2. Turn on antialiasing.
3. Watch it redraw.
	

Actual Results:  Very slow rendering of document (on a 1.3Ghz Athlon).

Additional info:

ggv doesn't suffer from the same slowness (but it can't open many PDFs that gv
can), nor did the version of gv that came with RH 7.2.

Comment 1 Sammy 2002-05-08 19:27:46 UTC

I have reported this earlier for rawhide...if you get the source rpm and 
remove the "alpha" patch it'll go back to being fast again. 
 
What version of gs are you using? I ask this because I am not sure why 
we have the alpha patch that seems to change some gs options.

Comment 2 Need Real Name 2002-05-08 19:43:21 UTC

I'm personally too lazy to mess with the source rpm, but thanks for the tip.

I'm using the version of ghostscript that comes with RH 7.3.
  $ rpm -q ghostscript
  ghostscript-6.52-8

Comment 3 Bill Nottingham 2002-06-12 05:48:17 UTC


*** This bug has been marked as a duplicate of 58978 ***