Hi Anna, Thank you very much for the reply. I found out that Chrome 10 has caused other people similar problems as it's now necessary to set a switch due to blacklisting of GPUs: I've got the to say yes, but my page still doesn't run. I'm now using Chrome 11.0.696.28 beta to make sure I'm up to date, and the javascript console gives the error as 'uncaught null processing.js: 2149. That line is: var fragmentShaderObject = curContext.createShader(curContext.FRAGMENT_SHADER); I'm not sure whether it might be due to GPU issues on my laptop, but at least it does work in FF4. It would be interesting to know if anyone else has the same issues with Chrome 10 though, as suggested in the chrome support site. Many thanks, Andrew.

On Apr 3, 3:58 pm, wrote: > Andrew, > First verify if webGL works in chrome at all. You can go to and see if the front page is a moving canvas or check out (google this if url is wrong) > > Anna > Sent on the TELUS Mobility network with BlackBerry > > > > > > > > -----Original Message----- annasob 5/4/2011, 10:21 น. Hi Anna, Thanks for the help. I'm using chrome 11.0.696.28 beta on linux mint 9, and I've used the latest stable version too. My graphics card is an Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07). It's not a hardware accelerated 3D card, but runs webgl fine in ff4 and previous versions of chrome.

Several bugs in Mac OpenGL drivers have been discovered by the WebGL team at Google. Apple fixes the bugs but the fixes are generally only available in the latest version of the OS AFAIK:( If the Chrome team decides the bugs are a security issue or if they affect WebGL compatibility in too many cases they have to blacklist that GPU on versions of the OS that still have the bug. Chrome definitely supports WebGL on OSX, and I can confirm that your Mac should work just fine. (I use one to develop WebGL in Chrome!) It sounds as if you may have accidentally disabled it somehow? Check in chrome://flags and see if 'Disable WebGL' flag has been set.

It might just be a glitch combining my hardware and the current version of chrome. I'll try chrome on Win7 on the same computer later too, to see if I get any errors your colleague didn't find. Many thanks, Andrew. On Apr 5, 6:21 pm, Anna Sobiepanek wrote: > Hey Andrew, > I got a colleague to run your url on Win 7 Chrome v10.0.648.204 and it > works with no errors. Can you please specify your computer specs: > Operating System, Graphics Card, Browser and Version.

If we can > replicate it then we can see if it is a processingjs bug or a Chrome > bug. > > Anna > > On Mon, Apr 4, 2011 at 3:00 PM, Andrew wrote: > > Hi Anna, > > > Thank you very much for the reply.

I found out that Chrome 10 has > > caused other people similar problems as it's now necessary to set a > > switch due to blacklisting of GPUs: > > >. Andrew 6/4/2011, 3:43 น. My passport for mac on pc. Hi again, Just a quick update.

I tried my url in chrome (stable version as of today) under Win7 and it runs with no problem. I've just installed the latest stable version of chrome (Version 10.0.648.204) on Mint 9 and I still get the uncaught exception error. So it's not the hardware but I suppose it might be a Mint 9 driver problem, but it's hard to know as I don't have any other PCs or linux versions to test with. How much is imovie for mac. It would be nice to know if this is just a little problem of my own, or a wider problem. Many thanks, Andrew.