[SOLVED] Memory access out of bound v1.52.3 issue

Help & Support
1

Hello :wave: ,

I have game which contains many rigidbody objects also i am adding removing rigidbody as well as i am also changing its type.
Those above mentioned things works fine in v1.51.7 and earlier versions.

But Now game in engine v1.52.3 game end up getting stuck with this error.

image
image1628×175 6.69 KB 

Uncaught RuntimeError: memory access out of bounds
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0xc8ac
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0xa279
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x520f5
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x2da4a
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x69c03
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x69b3d
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x33cf6
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x89a51
    at ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x2c6b7
    at x.stepSimulation (ammo.wasm.js?id=73109754&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=6b7ab3989e4f9f17c86e44380f9181c6:507:451)
$func206 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0xc8ac
$func164 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0xa279
$func1376 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x520f5
$func565 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x2da4a
$func1663 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x69c03
$func1661 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x69b3d
$func627 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x33cf6
$func1917 @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x89a51
$Uc @ ammo.wasm.wasm?id=73109755&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=a6819ea71a53e67f1dfe3e42957c2971:0x2c6b7
x.stepSimulation @ ammo.wasm.js?id=73109754&branchId=e1d29d14-3b4d-4f05-b8e6-5df34f9b79d3&t=6b7ab3989e4f9f17c86e44380f9181c6:507
onUpdate @ playcanvas.dbg.js?version=1.52.3:65125
fire @ playcanvas.dbg.js?version=1.52.3:759
update @ playcanvas.dbg.js?version=1.52.3:72235
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72821
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
requestAnimationFrame (async)
(anonymous) @ playcanvas.dbg.js?version=1.52.3:72802
2

hi @Ketan_ATA - would you be able to give me access to your project + repro steps? I’d be curious to find out which PR broke this, which would help point us towards a way to resolve this.

2 Likes
3

Thanks for the access. We’ve decided to go this way for now:

and will be releasing a patch soonish.

2 Likes
4

@mvaligursky Thank you!

1 Like
5

This patch was released today. Can you still if you still have this issue please?

1 Like
6

@yaustar It seems working fine now… Thank You!
v1.52.4 seems fixed those issues.

7

Hello @yaustar @mvaligursky, getting this issue now :frowning: