Bug 5148

Summary: [r300] Stale texture data used on first rendering
Product: Mesa Reporter: Eric Anholt <eric>
Component: Drivers/DRI/r300Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: glisse
Version: git   
Hardware: Other   
OS: FreeBSD   
Whiteboard:
i915 platform: i915 features:

Description Eric Anholt 2005-11-24 21:18:58 UTC 
A small sample app for this issue is from libpcg, tests/reactdiff_2d in TURING
mode (it's most visible there).  It's drawing a single texture that's evolving
over time.  After the texture has been updated, the first drawing of it will
draw four sub-triangles of (presumably) the first triangle drawn, using data
from the previous texture that was used.  Resizing the window to make it redraw
makes the misrendering go away.  It's somewhat visible while using the app, and
very prominent when quitting the app while the texture is light-colored, then
restarting.  The stale data will actually persist across X Server restarts.

Hacking up a fix for #5147 doesn't fix this.
Comment 1 Aapo Tahkola 2005-12-17 07:12:22 UTC 
z/c cache issues?
texenv seems to have similar problems.
Comment 2 Eric Anholt 2005-12-30 22:42:08 UTC 
Shouldn't be Z, since this demo (and texenv as well, afaik) doesn't use Z.
Comment 3 Aapo Tahkola 2006-01-05 21:04:16 UTC 
Looks like some ddx operation is causing this.
Moving another window on top of it makes it worse.
Comment 4 Aapo Tahkola 2006-01-21 09:02:06 UTC 
Should work a alot better now.

Multi texturing with s3tc still shows similar squares as nwn and texcmp
previously but I have not been able to figure out whats going on yet.
Comment 5 Aapo Tahkola 2006-08-23 11:56:03 UTC 
Fixed long time ago.
Comment 6 Adam Jackson 2009-08-24 12:23:37 UTC 
Mass version move, cvs -> git

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.