Ok, that is what the MODULARIZE option does. If that fixes it, then it does sound like the issue was related to the global Module object somehow. Although I am still unsure how a problem could occur.
- Alon On Mon, Jun 15, 2015 at 6:31 AM, Juergen Wothke <[email protected]> wrote: > I updated to 1.33.2 and still had the same effect. But then I found a > solution for my problem. After changing "my" original (see above) > MODULARIZE wrapper code to the below the problems all disapeared: > > window.SID_M= {} > var backend_SID = (function(Module) { > > [... EMSCRIPTEN generated code ...] > > return { > Module: Module, // expose original Module > }; > })(window.SID_M); > > > > On Monday, June 15, 2015 at 4:28:21 AM UTC+2, Alon Zakai wrote: >> >> Regarding the version, I don't remember any bugs related to that that >> were fixed since 1.13.0 (we are now on 1.33.2), but I'm not sure. >> >> - Alon >> > -- > 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
