# Mobile chrome fun

**URL:** <https://forum.babylonjs.com/t/mobile-chrome-fun/46432>\
**Category:** Questions\
**Created:** [December 14, 2023, 12:40pm UTC](https://forum.babylonjs.com/t/mobile-chrome-fun/46432 "2023-12-14T12:40:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Josip\_Almasi](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/josip_almasi/32/6391_2.png) [@Josip\_Almasi](https://forum.babylonjs.com/u/Josip_Almasi)\
**Post date:** [December 14, 2023, 12:40pm UTC](https://forum.babylonjs.com/t/mobile-chrome-fun/46432/1 "2023-12-14T12:40:51Z")

</div>

Hi,  
last weekend, my stuff stopped working on android… but not all, just some! 🙂  
Few days later, I’ve identified guilty party: [Chrome Releases: Chrome for Android Update](https://chromereleases.googleblog.com/2023/12/chrome-for-android-update.html) 120.0.6099.43

Basic scenes work fine, but as soon as anything dynamic goes on, it just does not render.  
For example, tap a mesh to load another mesh; AssetContainer.addAllToScene() and everything else works, but loaded mesh never renders. But much the same may happen with other dynamic everything.

But the fun only starts here 😉 Open a debug view, you can see all the the objects loaded in the tree. Better yet, when you select a node, it renders!  
Performance optimization gone wrong? 😉

So, is this something worth pursuing?

(I’m not very interested in pinpointing an android chrome issue myself, but I may spend some some more time on it if someone here is)

---

<div class="post-metadata">

**Author:** ![mawa](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/mawa/32/12384_2.png) [@mawa](https://forum.babylonjs.com/u/mawa)\
**Post date:** [December 14, 2023, 12:52pm UTC](https://forum.babylonjs.com/t/mobile-chrome-fun/46432/2 "2023-12-14T12:52:17Z")

</div>

Must be related to this ‘hot’ topic WIP

> [@Problems on Chrome Mobile since December 7th, 2023](https://forum.babylonjs.com/t/problems-on-chrome-mobile-since-december-7th-2023/46288):
>
> Hello, I hope everyone is well! I’m reporting this bug because I believe other people may experience it. I don’t think the problem is with Babylon, but rather with Chrome’s WebGL implementation. But I also write hoping that someone has some clue as to what it could be. Since yesterday, some users of my website (which uses Babylon.js v5.50.1) have been experiencing a strange problem when accessing through Chrome Mobile (Android, latest updated version: 120.0.6099.43). It doesn’t happen to ever…

Let me link it to it.