At IMVU, we've definitely seen scenarios where a browser occasionally fails to create a WebGL context. It seems to happen on a wide variety of hardware and operating systems. We see it internally a couple times a week. Sometimes it clears itself up, and sometimes a browser restart is required.
We haven't yet formulated a plan for how to deal with it, because, of course, this is something customers will run into. On Mon, Aug 25, 2014 at 9:56 AM, Floh <[email protected]> wrote: > Ok, latest info that the problem was caused by the long-running Chrome > browser. A reboot/restart fixed it. > > I'm suspecting a memory fragmentation issue, but since Chrome opens a new > process per tab it can't be the usual suspect (the emscripten heap), but > probably something in the GPU process which caused the WebGL context > creation to fail... > > Has anybody here experienced a problem like this? I'm not sure whether > it's worth writing a Chrome ticket with the little info I have. > > -Floh. > > Am Sonntag, 24. August 2014 17:42:15 UTC+2 schrieb Floh: > >> Ok thanks! I'll see if I can test a few more configs tomorrow at work. >> >> Cheers, >> -Floh. >> >> Am Sonntag, 24. August 2014 17:29:39 UTC+2 schrieb jj: >>> >>> There are no known Emscripten-specific GL context creation issues that >>> I'm aware of. Tested the Clear and Triangle samples on that site on the >>> following two systems, and on those they both pass: >>> >>> Mac mini >>> Late 2012 >>> >>> *Processor* 2.3 GHz Intel Core i7 >>> >>> *Memory* 4 GB 1600 MHz DDR3 >>> >>> *Graphics* Intel HD Graphics 4000 >>> >>> *Software* OS X 10.9.4 >>> >>> Chrome 36.0.1985.143 >>> >>> >>> MacBook Pro >>> >>> Retina, 15-inch, Early 2013 >>> >>> *Processor* 2.7 GHz Intel Core i7 >>> >>> *Memory* 16 GB 1600 MHz DDR3 >>> >>> *Graphics* NVIDIA GeForce GT 650M 1024 MB >>> >>> *Software* OS X 10.8.5 >>> >>> Chrome 36.0.1985.143 >>> >>> >>> >>> 2014-08-24 17:46 GMT+03:00 Floh <[email protected]>: >>> >>>> Hi, >>>> >>>> I got a report from a user with OSX Mavericks and integrated Intel plus >>>> dedicated NVIDIA GPUs that the WebGL context creation fails (at least in >>>> Chrome, I don't have info about other browser): >>>> >>>> "Could not create canvas: Web page was not allowed to create a WebGL >>>> context.,:(" >>>> >>>> Other WebGL demos run though, and use the NVIDIA GPU for rendering. Are >>>> there any known issues in emscripten WebGL context setup code (I'm using >>>> the new HTML5 setup functions) which would cause different behaviour from >>>> "traditional" WebGL demos? >>>> >>>> If anybody has a Mac with such a config (Intel+NVIDIA GPU + Chrome) I >>>> would be grateful for feedback whether these demos run: >>>> >>>> http://floooh.github.io/oryol/ >>>> >>>> Thanks! >>>> -Floh. >>>> >>>> >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "emscripten-discuss" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Chad Austin Technical Director, IMVU http://engineering.imvu.com <http://www.imvu.com/members/Chad/> http://chadaustin.me -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
