[Chromium-dev] Re: Visual problems and GLX (again)

[Mike H. <mho...@gr...>]

That works.  Removing the assertion doesn't quite do what we want since 
the render SPU still creates a bogus default window with the wrong 
visuals.  For some reason, we have a situation in which we try to set 
thing up before we have a window.

-Mike

Brian Paul wrote:

> Mike Houston wrote:
>
>> We seem to be back with issues getting correct visuals for certain 
>> apps like Raptor.  I'm hitting an assertion failure because the 
>> context->visBits are not matching window->visBits (assert fail on 
>> line 797 of readbackspu.c).  This only seems to occur when running 
>> CRUT based applications who do their window creation through CRUT.  
>> crut_ring.conf and crut_fan.conf are simpiler cases that exhibit this 
>> behavior.
>>
>> The context visbits are sane, but the window's visbits are zero (!).  
>> It seems that CRUT got broken along the way.  My guess is that window 
>> creation is failing oddly, but it's going to be awhile to track this 
>> down.  I'm currently running on ATI hardware, but I'd wager things 
>> are borked on Nvidia and 3DLabs as well.
>>
>> -Mike
>
>
> Mike, try this patch.
>
> diff -r1.21 readbackspu_init.c
> 68a69
> >       window->visBits = CR_RGB_BIT | CR_DEPTH_BIT | CR_DOUBLE_BIT;
>
> Or, I think you can simply disable the assertion for the time being.
>
> I think I know what the real problem is.  I'll work on a proper fix.
>
> -Brian