webarkit
Memory issue on multiple markers
I experienced that it is not stable in detection when there are multiple markers.
My case is now i have three markers and users need to scan one by one.
It works in iPhones even ip6s and some new model Androids.
However, a weird case happened in a flagship Android phone in 2018 (I guess not too old enough?)
Randomly two of the markers can be detected successfully but the remaining one is always cannot be detected.
Uncaught (in promise) RuntimeError: abort(RangeError: WebAssembly.instantiate(): Out of memory: wasm memory). Build with -s ASSERTIONS=1 for more info.
The phone didn't open a lot of apps or many tabs in Chrome. But still out of memory.
If it is simply a memory issue, is it possible to have a callback to know each marker loaded?
Now I can see two "loadNFTMarker -> 0" in console log but not three. I hope there are some callbacks to call so that I can somehow start some new flows for the fix. Thanks.
Anyone who faced this problem, a quick fix is to close the current tab and open a new one.
I can confirm this issue. I have different results by devices. With a old Wiko View i don't get that issue. Maybe something wrong with the Workers?
I noticed this error yesterday as well. It seems to be an issue with chrome, but only on mobile devices. Firefox seems to work fine. I'm trying to implement about 7 marker/images right now. But most likely even more in the future. Any fix for this issue would be great.
-- -- Perhaps an update of ARToolkitNFT 0.9.7 to a later version could fix this issue? Version 1.0.1 says "Enhanced PAGES_MAX. Now you can add up to 20 NFT markers." But it seems to be embedded in ARnft.js as BASE64 ArrayBuffer. -- --
Never mind, that's not the issue. Even if you break the wasm it's throws the memory error if it's more than 2 or 3 entities.
Okay, I played around with a super basic HelloWorld wasm, and as soon as I add the copiler argument "-s TOTAL_MEMORY=268435456" it will fire the out of memory message. I took the argument from the jsartoolkitnft makem.js file. Would it fix our issue, when we remove that line?
@tkapu Sorry for the delay, I'm very busy with my job at the moment, but i can confirm that i had this issue, randomly and not on every devices. The strange i had worste scenarios on newer Mobile devices (never had on desktop Pc). It could be that the Memory could cause some issues but it has also the compiler FLAG https://github.com/webarkit/jsartoolkitNFT/blob/fa5825cfe624d15f092e934b3a3459d827ba8afd/tools/makem.js#L176 that should allow to grow the Memory on demand. You should try to rebuild jsartoolkitNFT and then ARnft with the new args ( reducing the TOTAL_MEMORY). I would test but i have very limited time at the moment...
I lowered the total memory size in JsartoolkitNFT see PR #301 now the code is in the master branch i need to update ARnft dependencies as soon as i can.