# WASM memory access out of bounds using DracoLoader on Mobile Browsers

**URL:** <https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930>\
**Category:** Questions\
**Tags:** draco, gltf-loader, draco\_decoder, loaders, memory\
**Created:** [January 29, 2021, 12:49am UTC](https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930 "2021-01-29T00:49:05Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![mijofr](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/mijofr/32/19204_2.png) [@mijofr](https://discourse.threejs.org/u/mijofr)\
**Post date:** [June 28, 2021, 4:31am UTC](https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930/21 "2021-06-28T04:31:15Z")

</div>

Just to report in, I see the same issue across the draco-encoded glb models I use in my project on Android Chrome, never seen it on desktop browsers, models are all blender exports, generally a few hundred kilobytes compressed, around a meg uncompressed. Extremely inconsistent on if it happens or not, similar 80:20 success:fail rate, randomly across all models. The actual exception I get seems to vary too: sometimes it’s “memory access out of bounds”, sometimes it’s “table index is out of bounds”.

(Curious - do we have anyone reporting this on a gltf file instead of glb?)

---

<div class="post-metadata">

**Author:** ![gcope](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/gcope/32/14958_2.png) [@gcope](https://discourse.threejs.org/u/gcope)\
**Post date:** [June 28, 2021, 12:39pm UTC](https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930/22 "2021-06-28T12:39:23Z")

</div>

Also seeing this issue after updating to 1.3.6. Models that previously loaded fine fail with the same messages reported above about 20% of the time on Android Chrome.

---

<div class="post-metadata">

**Author:** ![Daniel\_Rodil](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/daniel_rodil/32/29701_2.png) [@Daniel\_Rodil](https://discourse.threejs.org/u/Daniel_Rodil)\
**Post date:** [September 21, 2022, 10:42am UTC](https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930/23 "2022-09-21T10:42:10Z")

</div>

I’m having the same issue with a gltf exported from blender that’s only 3.97Mb. I’ve tested in on chrome/desktop, firefox/desktop, firefox/android and it all works well, it’s only on chrome/android where the error happens. I reduced the model to 1.43Mb with the decimate modifier in blender and it loads well in chrome/android. I don’t know exactly what’s going on, for I’ve loaded much larger models and they load well…

[Previous page](https://discourse.threejs.org/t/wasm-memory-access-out-of-bounds-using-dracoloader-on-mobile-browsers/22930.md?page=1)