You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compiling an application using the Fetch API for >2GB max memory, the parameters to _emscripten_start_fetch: successcb, errorcb, progresscb, readystatechangecb are somehow dropped or optimized out. When the app does not pass a corresponding callback for these callbacks in the C/C++ side, this will result in the JS code trying to call these non-existent parameters, resulting in an error.
index.web.js:4028 Uncaught ReferenceError: readystatechangecb is not defined
at index.web.js:4028:74
at callUserCallback (index.web.js:3870:1)
at doCallback (index.web.js:4008:1)
at reportReadyStateChange (index.web.js:4027:1)
at xhr.onreadystatechange (index.web.js:3819:1)
The produced signature for _emscripten_start_fetch with max memory > 2GB:
function_emscripten_start_fetch(fetch){// ...}
The expected signature, produced with max memory <= 2GB:
When compiling an application using the Fetch API for >2GB max memory, the parameters to
_emscripten_start_fetch
:successcb
,errorcb
,progresscb
,readystatechangecb
are somehow dropped or optimized out. When the app does not pass a corresponding callback for these callbacks in the C/C++ side, this will result in the JS code trying to call these non-existent parameters, resulting in an error.The produced signature for
_emscripten_start_fetch
with max memory > 2GB:The expected signature, produced with max memory <= 2GB:
This can be reproduced using the test: https://github.com/emscripten-core/emscripten/blob/main/test/fetch/example_xhr_progress.c and compiling it with max memory > 2GB or <= 2GB and comparing the resulting signature for
_emscripten_start_fetch
Version of emscripten/emsdk:
Failing command line in full:
Full link command and output with
-v
appended:The text was updated successfully, but these errors were encountered: