model-viewer: "Memory access out of bounds" error on Chrome Mobile
Description
Hi!
Since last week we have been experimenting some errors on different projects that were working fine before. This is only happening on chrome mobile. All other browsers I have tested are working fine. Here’s the error msg I am getting in the console:
I am not sure this is is strictly from model viewer or from Chrome - WASM while trying to decompress Draco.
Live Demo
Here are some example links of pages that were working and now are experimenting this error: Live:
- https://molecularweb.epfl.ch/modules/atomic-structures/protein-interactions/
- https://molecularweb.epfl.ch/modules/biological-assemblies/ribosome/ribosome.html
- https://1gd2.glitch.me/
Code:
- https://github.com/fcor/molecular-mirror-app/blob/master/modules/biological-assemblies/ribosome/ribosome3d.html
- https://glitch.com/edit/#!/1gd2
Version
- model-viewer: v1.7.2
Browser Affected
- Chrome, version: 91.0.4472.101
- Edge
- Firefox
- IE
- Safari
OS
- Android
- iOS
- Linux
- MacOS
- Windows
AR
- WebXR
- SceneViewer
- QuickLook
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19
Thanks, I have a repro now too, Pixel 4 Android 11, Chrome 91. Chrome 90 seems fine. We’re looking into it with the Chrome team now.
And it’s a static property, so don’t forget this line:
ModelViewerElement = self.ModelViewerElement || {};https://modelviewer.dev/examples/loading/#dracoSupportHi @gjcope and @fcor We uploaded version 1.4.2 of our draco decoders here: https://www.gstatic.com/draco/versioned/decoders/1.4.2/
Basically this is 1.4.1 but we set INITIAL_MEMORY to 64mb, which worked with one of your models. So this is only a workaround, because if a specific models needs > 64MB memory to decode then we will hit the issue again.
Can you try setting model-viewer to point to 1.4.2? E.g. ModelViewerElement.dracoDecoderLocation = ‘https://www.gstatic.com/draco/versioned/decoders/1.4.2/’;
Definetly works for now! Samsung S9