[Web] The ONNX model cannot be loaded via WASM in the IOS17 browser.

[zyhhahah]

Describe the issue

This is the encountered error, which only occurs in the web environment on the iPhone.

I initially thought this issue was caused by version differences, so I tried many versions. They all worked fine in the web environment on Android and Windows. Based on the error message, it seems to be caused by insufficient memory. I tried many different models, including some very small ones, but the issue persisted. However, I found that when using the WebGL backend, the issue does not occur. It only happens with the WASM backend.

To reproduce

In my project, the code is quite complex, so I simplified it following the official example to reproduce the issue. The model used can be any ONNX model. The devices I tested on include iPhone 13 Pro, iPhone 13 Pro Max, and iPhone 15 Pro Max, and the issue occurred on all of them.

Urgency

My project is currently at a standstill due to this issue, and I'm not sure whether it's a problem with my implementation or a version-related issue. I'm wondering if I'm the only one encountering this problem.

ONNX Runtime Installation

Built from Source

ONNX Runtime Version or Commit ID

多版本都存在这个问题

Execution Provider

'webgl' (WebGL), 'wasm'/'cpu' (WebAssembly CPU)

[transcranial]

We are also seeing this exact error with onnxruntime-web 1.19.0, running a tiny model in all browsers on iOS 17.6.1 as well as iPadOS 17.6.1. Works fine in all browsers including safari on macOS. Downgrading onnxruntime-web to 1.18.0 fixes this for us.

[satyajandhyala]

The Out of Memory error was previously reported and fixed by rolling back Emscripten SDK upgrade, backe to 3.1.59. Did reproduce this error with the latest code on main branch?

[zyhhahah]

我们在 onnxruntime-web 1.19.0 中也看到了同样的错误，在 iOS 17.6.1 和 iPadOS 17.6.1 上的所有浏览器中运行了一个小模型。在包括 macOS 上的 Safari 在内的所有浏览器中都可以正常工作。将 onnxruntime-web 降级到 1.18.0 可以为我们解决这个问题。

Thank you for your help. The issue indeed doesn't exist in version 1.18.0, it seems I carelessly missed this during my earlier attempts. I really appreciate your reminder.

[zyhhahah]

之前曾报告过内存不足错误，并通过将 Emscripten SDK 升级回滚到 3.1.59 来修复。是否使用主分支上的最新代码重现了此错误？

Hello, I tried using the latest code as per your suggestion. Unfortunately, the same error still occurs.

[fs-eire]

@zyhhahah could you help to test whether the following versions work or not:

• 1.20.0-dev.20240919-bd60add8ce
• 1.19.2
• 1.18.0

[zyhhahah]

@fs-eire I tested these three versions on various platforms.

• 1.20.0-dev.20240919-bd60add8ce ==> on iOS system no available backend found. ERR: [wasm] RangeError: Out of memory

• 1.19.2 ==> on iOS system no available backend found. ERR: [wasm] RangeError: Out of memory

• 1.18.0 ==> success

• 1.18.0 ==> But there's one thing I'm not sure is a potential issue: when I enable crossOriginIsolated mode, my iPhone still encounters an out-of-memory problem, and it only runs normally when I manually set wasm.numThreads to 1. wasm.numThreads cannot be set to the default value or a number greater than 1.

[fs-eire]

I think this is a known issue of Safari and it is fixed in iOS v18.0: emscripten-core/emscripten#19374

Screenshot from BrowserStack - https://jsfiddle.net/tpz1k9d7/3/

iOS 17:

iOS 18:

[zyhhahah]

@fs-eire Thank you for your reminder. I have also tested it and confirmed that indeed in iOS 18 this issue does not occur, so my question can be closed.

[ohnobug]

work for me

important!!!

yarn add [email protected] or npm install [email protected]

import * as ort from 'onnxruntime-web';
ort.env.wasm.wasmPaths = "https://cdnjs.cloudflare.com/ajax/libs/onnxruntime-web/1.17.3/"
ort.env.wasm.simd = false;
ort.env.wasm.numThreads = 1;
ort.env.debug = true;

[jayanth0107]

@ohnobug resource not found for wasmPath provided above - https://cdnjs.cloudflare.com/ajax/libs/onnxruntime-web/1.17.3/

[ohnobug]

@jayanth0107 or use https://cdn.jsdelivr.net/npm/[email protected]/dist/
??

package page:
https://www.jsdelivr.com/package/npm/onnxruntime-web?version=1.17.3
https://www.jsdelivr.com/package/npm/onnxruntime-web?version=1.17.3&tab=files&path=dist

[fs-eire]

Yes, you can use jsdelivr which still have version 1.17.3 available.

By the way, onnxruntime-web no longer release webassembly artifacts for non-SIMD and non-MultiThread since version 1.18. While you can use onnxruntime v1.17.3 as a compatibility workaround for ios17.

[jbrough]

This issue has reoccurred in the 1.22.0 release

[fs-eire]

@jbrough could you describe it more about "issue has reoccurred in the 1.22.0 release"? Is it v1.21.1 working but v1.22.0 not working on a specific iOS version ?

[jbrough]

@fs-eire yes, sorry I tried to find this thread again to provide more info. v1.21.1 worked. v1.22.0 does not on iOS (v18), when the cdn switched it out a few days ago, that's when I noticed the issue: OOM Range Error, as above.

Compiling to wasm myself with these flags fixes it on Safair IOS18

onnxruntime_EMSCRIPTEN_SETTINGS="MALLOC=dlmalloc;STACK_SIZE=1048576;INITIAL_MEMORY=67108864;ALLOW_MEMORY_GROWTH=1;MAXIMUM_MEMORY=201326592"

I think if I went much above 196MB max shared memory the bug would re-occur but I didn't test that yet,

[jbrough]

to summarise, the shared memory max defaults are prob a hair too high for iOS - the initial memory isn't important, whatever the maximum memory is if ALLOW_MEMORY_GROWTH=1 is what safari takes into account.

I have tested this and have it working again with SileroVAD after compiling the threaded wasm myself with those revised memory limits.