[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Chrome stable linux



----- Original Message -----
> For me, Firefox seems to be running just great on this setup...that
> is,
> until my driver gets blacklisted. :-(

Are you running a 32bit build? The crash reports we've received were all in 64bit builds. So it's conceivable to un-block this driver version on 32bit builds. I just amn't sure that it's worth the risk (it might not crash but still be a poor experience).

> 
> Is it necessary to blacklist all of the 260.19.* releases?

We definitely have had many crash reports at least with 260.19.06 and 260.19.36. Given that it was not limited to one sub-version, I went ahead and blacklisted all of 260.19.

> 
> The trouble is that nVidia's latest Linux driver is 260.19.36 (which
> is
> just a couple of weeks old). I'm seeing problems in 260.19.12 (which
> is
> from last October...and then, only in Chrome). Users have no upgrade
> path. Is there an older driver that's not blacklisted?

For the NVIDIA linux driver, 260.19 is the only version that we blacklist. Anything else works (here I'm admitting that we haven't implemented the blocking of old drivers on linux as we have on Windows).

> Has anyone talked to nVidia?

No, but we should. Pinging relevant people.

Benoit



> 
> -- Steve
> 
> 
> On 02/12/2011 03:21 PM, Mo, Zhenyao wrote:
> > Did Firefox demonstrate the same behavior? Or it runs all those
> > demos
> > fine in Firefox?
> >
> > Mo
> >
> > On Sat, Feb 12, 2011 at 11:33 AM, Steve Baker <steve@sjbaker.org>
> > wrote:
> >
> >> On 02/12/2011 08:17 AM, Mo, Zhenyao wrote:
> >>
> >>> Can you download the latest linux build and give it a try?
> >>> http://build.chromium.org/f/chromium/continuous/?C=N;O=D
> >>>
> >>> I just created a bug in chromium to track this:
> >>> http://code.google.com/p/chromium/issues/detail?id=72815
> >>>
> >>>
> >> I did that - and the result was kinda exciting...so I thought you'd
> >> like
> >> a screenshot (see below)...after about three or four "reloads", it
> >> eventually came up and said "Your browser supports WebGL!" (which,
> >> I
> >> have to say is a bit of an exaggeration right now!)
> >>
> >> The "shiney teapot" demo comes up with "no webgl" - but, again, if
> >> I
> >> reload, it works OK. Everything seems very fragile.
> >>
> >> The output from 'about:gpu' is now:
> >>
> >> Data exported Sat Feb 12 2011 13:19:57 GMT-0600 (CST)
> >> Chrome version 11.0.670.0 (Developer Build 74731)
> >>
> >>
> >>      Driver Information
> >>
> >> Initialization time 612
> >> Vendor Id 0x10de
> >> Device Id 0x0041
> >> Driver vendor NVIDIA
> >> Driver version 260.19.12
> >> Pixel shader version 1.20
> >> Vertex shader version 1.20
> >> GL version 2.1
> >> GL_VENDOR NVIDIA Corporation
> >> GL_RENDERER GeForce 6800/AGP/SSE2
> >> GL_VERSION 2.1.2 NVIDIA 260.19.12
> >>
> >> ...then a bunch of extensions...then:
> >>
> >>
> >>      Diagnostics
> >>
> >> None
> >>
> >>
> >>      Log Messages
> >>
> >>    * [2036:2036:849014848678:INFO:gl_implementation.cc(95)] : Using
> >>      desktop GL implementation.
> >>    * [2036:2036:849015418755:INFO:gpu_thread.cc(122)] :
> >>    gpu_info_collector::CollectGraphicsInfo
> >>      complete
> >>
> >>
> >> Here is the screenshot from the first call to
> >> http://get.webgl.org...(!!)
> >>
> >>
> >>
> >>
> 
> -----------------------------------------------------------
> You are currently subscribed to public_webgl@khronos.org.
> To unsubscribe, send an email to majordomo@khronos.org with
> the following command in the body of your email:
> unsubscribe public_webgl
> -----------------------------------------------------------
-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------