Alright, I'll try to simplify the program tomorrow and get back to you.
On Thursday, September 14, 2017 at 10:04:02 PM UTC+2, Alon Zakai wrote:
>
> Ok, you may be hitting an unknown bug then. Can you provide a testcase
> showing the issue? If not, I would debug this by adding a bunch of
> console.logs in relevant places (where Module.asm is assigned to, where you
> start the call that aborts, etc.).
>
> On Thu, Sep 14, 2017 at 12:50 PM, Dirk Vanden Boer <dirk...@gmail.com
> <javascript:>> wrote:
>
>> I already built with -s ASSERTIONS=1 as it was a suggestion in the error,
>> but it doesn't seem to change anything.
>>
>> I'm waiting for the onRuntimeInitialized callback before doing calls.
>>
>> This is also printed in the console:
>> uncaught exception: abort({}) at jsStackTrace@http://
>> 127.0.0.1:8080/gdx-wasm.js:1:33098
>> stackTrace@http://127.0.0.1:8080/gdx-wasm.js:1:33269
>> abort@http://127.0.0.1:8080/gdx-wasm.js:1:333639
>> doNativeWasm/<@http://127.0.0.1:8080/gdx-wasm.js:1:46926
>>
>>
>>
>>
>> On Thursday, September 14, 2017 at 9:29:33 PM UTC+2, Alon Zakai wrote:
>>>
>>> I would guess there is a too-early call into compiled code, confounded
>>> by a timing issue, and it happens one browser's startup is slower and is
>>> after Module.asm exists, so it seems to work there. To check that theory,
>>> try a build with -s ASSERTIONS=1 , that should check calls at runtime. If
>>> it is in fact the case, see
>>> http://kripken.github.io/emscripten-site/docs/getting_started/FAQ.html#how-can-i-tell-when-the-page-is-fully-loaded-and-it-is-safe-to-call-compiled-functions
>>>
>>>
>>>
>>>
>>> On Thu, Sep 14, 2017 at 11:10 AM, Dirk Vanden Boer <dirk...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I created a webassembly project that runs fine in Google Chrome, but in
>>>> firefox I get the following error:
>>>>
>>>> failed to asynchronously prepare wasm: TypeError: Module.asm is
>>>> undefined gdx-wasm.js:1:17745
>>>> TypeError: Module.asm is undefined
>>>> Stack trace:
>>>> Module.__GLOBAL__I_000101@http://127.0.0.1:8080/gdx-wasm.js:1:316269
>>>> func@http://127.0.0.1:8080/gdx-wasm.js:1:50681
>>>> callRuntimeCallbacks@http://127.0.0.1:8080/gdx-wasm.js:1:37234
>>>> ensureInitRuntime@http://127.0.0.1:8080/gdx-wasm.js:1:37753
>>>> doRun@http://127.0.0.1:8080/gdx-wasm.js:1:332118
>>>> run@http://127.0.0.1:8080/gdx-wasm.js:1:332558
>>>> runCaller@http://127.0.0.1:8080/gdx-wasm.js:1:330813
>>>> removeRunDependency@http://127.0.0.1:8080/gdx-wasm.js:1:42608
>>>> receiveInstance@http://127.0.0.1:8080/gdx-wasm.js:1:46417
>>>> doNativeWasm/<@http://127.0.0.1:8080/gdx-wasm.js:1:46794
>>>>
>>>> Any hints on how to fix this?
>>>>
>>>> Thanks
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "emscripten-discuss" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to emscripten-discuss+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to emscripten-discuss+unsubscr...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to emscripten-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
