Bug 25748 - Paraview text labels overdrawn when using hardware rendering
Summary: Paraview text labels overdrawn when using hardware rendering
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i915 (show other bugs)
Version: 7.6
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Eric Anholt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-21 14:31 UTC by Andrew Lofthouse
Modified: 2010-02-04 05:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Labels overdrawn when used with hardware rendering (119.26 KB, image/png)
2009-12-21 14:31 UTC, Andrew Lofthouse
Details
Screenshot showing correct rendering without hardware acceleration (121.33 KB, image/png)
2009-12-21 14:33 UTC, Andrew Lofthouse
Details

Description Andrew Lofthouse 2009-12-21 14:31:52 UTC
Created attachment 32231 [details]
Labels overdrawn when used with hardware rendering

When using Paraview 3.6.1 with Mesa using hardware rendering, as shipped with Fedora 12, legend labels (and other labels) are overdrawn (see attachment).  When MesaLib-0.7.6-1rc4 is compiled without hardware rendering (using the generic linux-86-64 target), the problem is not present.  (I'll attach a screenshot of what it is supposed to look like.)  I've also verified that the problem exists when using the latest Mesa from git (as of 20091219).

Others using ParaView with Fedora 12 have verified that the label overdrawing does not occur with non-intel cards (see the thread on the paraview mailing list at http://www.paraview.org/pipermail/paraview/2009-December/015031.html).

It seems that the code in question is related to freetype and GL (see http://www.paraview.org/pipermail/paraview/2009-December/015087.html).
Comment 1 Andrew Lofthouse 2009-12-21 14:33:35 UTC
Created attachment 32232 [details]
Screenshot showing correct rendering without hardware acceleration
Comment 2 Eric Anholt 2009-12-29 09:54:45 UTC
Has this always occurred?  Could someone come up with a small testcase to show the problem?
Comment 3 Andrew Lofthouse 2010-01-01 11:39:49 UTC
This problem hasn't always existed -- but I'm not sure when it started.  Going back and trying to verify (using the Live CDs): it does not exist with a clean install of Fedora 10 (Mesa 7.2, git 20081001).  It also does not exist with a clean install of Fedora 11 (Mesa 7.5, git 20090428).  As I recall, the updated version of Fedora 11 causes the problem (Mesa 7.6, git 20090612) -- I can't verify because I don't have Fedora 11 currently installed, and I can't get the updates to work with only the Live CD.  The problem does exist with a clean install of Fedora 12 (Mesa 7.6, git 20090921).

I'm not familiar enough with GL programming to come up with a small test case without some significant time investment...
Comment 4 Eric Anholt 2010-01-30 12:57:13 UTC
In the absence of a testcase, git-bisect is the way to find what went wrong.  Someone will have to do it.
Comment 5 Andrew Lofthouse 2010-02-04 05:50:51 UTC
I tried to reproduce this error in order to git-bisect, but was unable to with the latest Fedora updates.  It seems that somewhere along the line this has been fixed...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.