Bug 2093

Summary: Unichrome / Mesa: Drawable changes sometimes not gets through.
Product: Mesa Reporter: Thomas Hellström <thomas>
Component: Drivers/DRI/UnichromeAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high    
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Thomas Hellström 2004-12-16 12:53:19 UTC
If windows with dri rendering are abruptly resized, the changes sometimes not
get through to the driver as it should. 
Example: glxgears:

If the window is resized, the contets usually follows the window but there seems
to be some kind of lag in the back-buffer size as the last lines sometimes are
white. Under certain conditions there can be a number of white lines, while the
gears are picking up the change and drawn over the whole window.

If The maximize-window is clicked, sometimes not even the back-buffer stride
takes effect and a number of repetitative glxgears are drawn. The back-to-front
blit seems OK, though.

Mostly tested in 1280x1024x24
Comment 1 Ian Romanick 2004-12-16 17:32:13 UTC
Could this be related to #1556?  My CLE266 box is now gone, so I can't do
anymore testing on it. :(

https://bugs.freedesktop.org/show_bug.cgi?id=1556
Comment 2 Thomas Hellström 2004-12-17 01:29:57 UTC
(In reply to comment #1)
> Could this be related to #1556?  My CLE266 box is now gone, so I can't do
> anymore testing on it. :(
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=1556
> 

Yes possibly, I think there were a number of bugs in play here. I fixed a
blitter context bug that seemed to cure also 1556 but then this emerged. I think
this one might be related to the new way Mesa signals drawable changes to the
driver.
Comment 3 Thomas Hellström 2004-12-29 09:14:26 UTC
Apparently fixed by Keith in latest CVS.
Comment 4 Adam Jackson 2009-08-24 12:22:56 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.