# Babylonjs not working on Chrome 108.0.5359.94 **URL:** \ **Category:** Bugs\ **Created:** [December 6, 2022, 10:22pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323 "2022-12-06T22:22:43Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![deslancers](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deslancers/32/17620_2.png) [@deslancers](https://forum.babylonjs.com/u/deslancers)\ **Post date:** [December 6, 2022, 10:22pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/1 "2022-12-06T22:22:43Z")
Hello community! I found strange issue, in my chrome any of babylon based project not worked, even a playground examples from main page. First of all i went to about:flags and check WebGL, then about:gpu in results all enabled and works. Then i went to Threejs examples and to my surprise it works. Attached archive with reports. My hardware - Laptop MSI katana with Intel 11800H, GeForce 3060ti OS - Kubuntu 22.04LTS; Maybe anyone know how can i fix it? [report.zip](https://forum.babylonjs.com/uploads/short-url/8zsUYW2HX1szGzmBKSdNnztTriG.zip) (1.2 MB) ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [December 6, 2022, 10:33pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/2 "2022-12-06T22:33:45Z")
Ohhhhh that sounds pretty bad… @Cedric or @bghgary do you have a ubuntu to test on ??? Would be great if anybody else in the community can try ? webgl not supported means a simple canvas.getContext(“webgl”, options) is not working so one of the options is breaking it but which one is the issue… ---
**Author:** ![bghgary](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/bghgary/32/48532_2.png) [@bghgary](https://forum.babylonjs.com/u/bghgary)\ **Post date:** [December 6, 2022, 10:45pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/3 "2022-12-06T22:45:18Z")
I only have Ubuntu in a VM, but the playground is working with Chrome for me. ```auto Google Chrome 108.0.5359.94 (Official Build) (64-bit) Revision 713576b895246504ccc6b92c2fb8ce2d60194074-refs/branch-heads/5359_71@{#3} OS Linux JavaScript V8 10.8.168.21 ``` ```auto $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.5 LTS Release: 20.04 Codename: focal ``` ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [December 6, 2022, 10:56pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/4 "2022-12-06T22:56:27Z")
@deslancers would be great if you could report on the chromium bug tracker and check if mozilla is having the same issue ? ---
**Author:** ![deslancers](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deslancers/32/17620_2.png) [@deslancers](https://forum.babylonjs.com/u/deslancers)\ **Post date:** [December 6, 2022, 11:07pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/5 "2022-12-06T23:07:13Z")
I have this issue a few weeks, currently i work and test my projects in mozilla without any issues, this bug i found in last updated chrome. I’ll create report on bug tracker. Also i tested chrome the same version on Windows 11 and it works fine. Looks like problem with linux package. ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [December 6, 2022, 11:10pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/6 "2022-12-06T23:10:21Z")
yup and not all dist as ubuntu LTS seems to be doing okay ☹ ---
**Author:** ![deslancers](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deslancers/32/17620_2.png) [@deslancers](https://forum.babylonjs.com/u/deslancers)\ **Post date:** [December 6, 2022, 11:22pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/7 "2022-12-06T23:22:36Z")
I rollback chrome to 106 and now all works fine! ![Screenshot_20221207_012153](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/3X/8/9/895959b0d17b5ce6bab7137c18faa35275090439.png) ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [December 6, 2022, 11:26pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/8 "2022-12-06T23:26:36Z")
so definitely seems on their hand unfortunately ☹ ---
**Author:** ![7om](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/7om/32/11158_2.png) [@7om](https://forum.babylonjs.com/u/7om)\ **Post date:** [December 7, 2022, 11:01am UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/9 "2022-12-07T11:01:41Z")
Try to disable the Vulkan backend here: chrome://flags/#enable-vulkan It seems like the Intel Vulkan drivers are causing this issue (which would also mean that you are not using your NVIDIA GPU, but the i-GPU instead). ---
**Author:** ![7om](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/7om/32/11158_2.png) [@7om](https://forum.babylonjs.com/u/7om)\ **Post date:** [December 7, 2022, 11:09am UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/10 "2022-12-07T11:09:26Z")
Well, it’s complicated. It seems like Chrome started using the Vulkan backend if available (since about 107) and in the case of an Intel iGPU this seems to be broken. The root cause would then be a faulty Intel driver… or its integration which would then be Google turf again. 🤔 Most likely related to this issue: > [@Performance and rendering issues since Fedora 37 upgrade](https://forum.babylonjs.com/t/performance-and-rendering-issues-since-fedora-37-upgrade/35739): > > I upgraded to Fedora 37 and now all Babylon-related rendering is flickering (with a bright interframe) and the browser seems to be struggling because of high CPU load. Almost any other WebGL(2) content is rendering just as before (e.g. three.js-based). I tested dozens of demos from [Chrome Experiments - Experiments with Google](https://experiments.withgoogle.com/collection/chrome) and [https://avseoul.net/particleEqualizer](https://avseoul.net/particleEqualizer) was the only one I could find with similar issues. WebGL Report output for WebGL2: Platform: Linux x86\_64 Browser User Agent… ---
**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\ **Post date:** [December 7, 2022, 5:43pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/11 "2022-12-07T17:43:23Z")
Thanks for the info @7om hope they can address those issues soon. ---
**Author:** ![deslancers](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/deslancers/32/17620_2.png) [@deslancers](https://forum.babylonjs.com/u/deslancers)\ **Post date:** [December 12, 2022, 2:49pm UTC](https://forum.babylonjs.com/t/babylonjs-not-working-on-chrome-108-0-5359-94/36323/12 "2022-12-12T14:49:07Z")
HI! I disable Vulkan in Chrome and now it works as expected, thank you! ![Screenshot_20221212_165004](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/3X/c/0/c0fad7f52f35b815c6913c121cdd125c667cad09.png)