# Error constructing CesiumWidget.

**URL:** <https://community.cesium.com/t/error-constructing-cesiumwidget/4746>\
**Category:** CesiumJS\
**Created:** [October 24, 2016, 10:28pm UTC](https://community.cesium.com/t/error-constructing-cesiumwidget/4746 "2016-10-24T22:28:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nico\_Deufemia](https://avatars.discourse-cdn.com/v4/letter/n/bcef8e/32.png) [@Nico\_Deufemia](https://community.cesium.com/u/Nico_Deufemia)\
**Post date:** [October 24, 2016, 10:28pm UTC](https://community.cesium.com/t/error-constructing-cesiumwidget/4746/1 "2016-10-24T22:28:23Z")

</div>

Hey guys,

I just recognized that kinda all websites with CesiumJS running, even [CesiumJS.org](http://CesiumJS.org) deliver following Error:

Error constructing CesiumWidget.

Visit [http://get.webgl.org](http://get.webgl.org/) to verify that your web browser and hardware support WebGL. Consider trying a different web browser or updating your video drivers. Detailed error information is below:  
RuntimeError: The browser supports WebGL, but initialization failed.

(…)

``

I am one of two developers behind [https://social-journey.com/](https://social-journey.com/) .

How can this error be resolved??

My browser (Chrome Version 55.0.2883.21 beta-m (64-bit)) definetly supports hardware accelerated WebGL and so does my hardware.

Graphic card drivers are uptodate (nvidia 341.98) and working properly.

Thanks in advance!

Greetz,

Nico

---

<div class="post-metadata">

**Author:** ![hannah](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/hannah/32/4509_2.png) [@hannah](https://community.cesium.com/u/hannah)\
**Post date:** [October 25, 2016, 1:52pm UTC](https://community.cesium.com/t/error-constructing-cesiumwidget/4746/2 "2016-10-25T13:52:21Z")

</div>

Hello Nico,

It sounds like your running into this issue: [https://github.com/AnalyticalGraphicsInc/cesium/issues/4442](https://github.com/AnalyticalGraphicsInc/cesium/issues/4442)

We’re pretty sure it’s a bug in the latest version of Chrome. In the meantime, have you tried using firefox?

Best,

Hannah
