# Issue with viewer.model.setNodeMatrix(nodeId, result) on Root Node of Large Model

**URL:** https://forum.techsoft3d.com/t/issue-with-viewer-model-setnodematrix-nodeid-result-on-root-node-of-large-model/4532
**Category:** HOOPS Visualize Web
**Tags:** code, webviewer
**Created:** [April 9, 2025, 5:43am UTC](https://forum.techsoft3d.com/t/issue-with-viewer-model-setnodematrix-nodeid-result-on-root-node-of-large-model/4532 "2025-04-09T05:43:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![raja.r](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@raja.r](https://forum.techsoft3d.com/u/raja.r)
#### Post date: [April 9, 2025, 5:43am UTC](https://forum.techsoft3d.com/t/issue-with-viewer-model-setnodematrix-nodeid-result-on-root-node-of-large-model/4532/1 "2025-04-09T05:43:50Z")

</div>

Hi everyone,

I’m encountering an issue when trying to run the following code:

```auto
try {
  await viewer.model.setNodeMatrix(nodeId, result);
} catch (error) {
  console.log('IafMathUtils.translateNode', error);
}

```

This works fine on smaller nodes, but when I attempt it on the **root node of a large model** , I receive the following error:

```auto
abort("Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X 
with X higher than the current value 2147418112, 
(2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime, 
or (3) if you want malloc to return NULL (0) instead of this abort, 
compile with -s ABORTING_MALLOC=0 "). 
Build with -s ASSERTIONS=1 for more info.

```

### ❓ Questions:

- Is this related to WebAssembly memory limits? if so how to address?
- Any other suggested workarounds when working with large models in a viewer?

---

<div class="post-metadata">

### Author: ![tino](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@tino](https://forum.techsoft3d.com/u/tino)
#### Post date: [April 9, 2025, 9:38am UTC](https://forum.techsoft3d.com/t/issue-with-viewer-model-setnodematrix-nodeid-result-on-root-node-of-large-model/4532/2 "2025-04-09T09:38:36Z")

</div>

Hello @raja.r,

Which version of Communicator are you using?

Thanks,  
Tino

---

<div class="post-metadata">

### Author: ![raja.r](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@raja.r](https://forum.techsoft3d.com/u/raja.r)
#### Post date: [April 10, 2025, 5:00am UTC](https://forum.techsoft3d.com/t/issue-with-viewer-model-setnodematrix-nodeid-result-on-root-node-of-large-model/4532/3 "2025-04-10T05:00:06Z")

</div>

We’re currently on **2023 SP1**

---

<div class="post-metadata">

### Author: ![tino](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@tino](https://forum.techsoft3d.com/u/tino)
#### Post date: [April 10, 2025, 5:14am UTC](https://forum.techsoft3d.com/t/issue-with-viewer-model-setnodematrix-nodeid-result-on-root-node-of-large-model/4532/4 "2025-04-10T05:14:40Z")

</div>

With the release of HC 2024.5.0, as noted in our [release notes](https://docs.techsoft3d.com/communicator/latest/release_notes/2024.5.0.html#fixed-bugs), we fixed an issue where memory usage increased significantly (which is similar to your situation):

 ![image](https://us1.discourse-cdn.com/flex020/uploads/techsoft3d/original/2X/2/29d5ec3e47b4207386f0f0964ede8a34b42a019f.png)

If possible, please test on more recent version of Communicator.

Thanks,  
Tino