# Sudden error during Engine initialization on Chrome

**URL:** <https://forum.babylonjs.com/t/sudden-error-during-engine-initialization-on-chrome/5325>\
**Category:** Questions\
**Created:** [August 27, 2019, 8:44pm UTC](https://forum.babylonjs.com/t/sudden-error-during-engine-initialization-on-chrome/5325 "2019-08-27T20:44:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stealman](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/stealman/32/340_2.png) [@stealman](https://forum.babylonjs.com/u/stealman)\
**Post date:** [August 27, 2019, 8:44pm UTC](https://forum.babylonjs.com/t/sudden-error-during-engine-initialization-on-chrome/5325/1 "2019-08-27T20:44:07Z")

</div>

Hello guys, I am not sure whether this is a bug or not. But suddenly without any change, Babylon JS stopped to work in Chrome.

It worked for several weeks (I didnt change anything) and suddenly it does not work anymore - thus it must be something related to Chrome, because it does work in Firefox and in IE.

Error says this: Uncaught TypeError: this.\_caps.parallelShaderCompile.maxShaderCompilerThreadsKHR is not a function

You can see it on this URL: [https://darkenlight.net:8080/spaceY/](https://darkenlight.net:8080/spaceY/)

Do you have some idea about what is wrong ?

I have Babylon version Babylon.js v4.0.0-alpha.19 - WebGL2

Thanx very much !!!

---

<div class="post-metadata">

**Author:** ![Gijs](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/gijs/32/44_2.png) [@Gijs](https://forum.babylonjs.com/u/Gijs)\
**Post date:** [August 27, 2019, 9:15pm UTC](https://forum.babylonjs.com/t/sudden-error-during-engine-initialization-on-chrome/5325/2 "2019-08-27T21:15:36Z")

</div>

Hi, this is because of a change in Chrome, see:

> [@Bug from nowWhere + Bug with 4.1.0](https://forum.babylonjs.com/t/bug-from-nowwhere-bug-with-4-1-0/5061/2):
>
> the 4.0 issue comes from a change in Chrome regarding shader compilation. The spec evolved. So moving to 4.1 is a good idea For your 4.1 bug, simply set a breaking at Scene.\_evaluateActiveMeshes (scene.ts:3365) or even better set your f12 debugger to break on all exception so the debugger will be triggered when the error will be hit

---

<div class="post-metadata">

**Author:** ![stealman](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/stealman/32/340_2.png) [@stealman](https://forum.babylonjs.com/u/stealman)\
**Post date:** [August 27, 2019, 9:17pm UTC](https://forum.babylonjs.com/t/sudden-error-during-engine-initialization-on-chrome/5325/3 "2019-08-27T21:17:06Z")

</div>

Thanx very much ! I will give it a try !