That should not happen, sounds like there might be a bug in emscripten somewhere.
The only shared state that should exist is the global Module object itself, which connects print to an HTML element and so forth. But that should not cause problems like these. Please try to narrow this down to as small a testcase as you can, and file an issue. - Alon On Sun, Jun 14, 2015 at 4:19 PM, Juergen Wothke <[email protected]> wrote: > I have done a generic WebAudio based music player where various > independent backends (that produce the actual sample data) can be plugged > in. > Most of the backends are implemented using Emscripten and I am using an > approach like the "MODULARIZE" feature of more > recent EMSCRIPTEN versions to avoid name clashes, e.g. > > var backend_SID = (function() { > > [..... original code generated by Emscripten...] > > return { > Module: Module // expose original Module > }; > })(); > > As long as only one of these "backend" modules is loaded on a page the > logic works flawlessly. But as soon as I load a 2nd "backend" on the same > page, then the 1st "backend" seems to get corrupted.. It looks as if there > is some global state that both modules are sharing.. > > Is this a known issue to do with the old version (emsdk-1.13.0) that I am > still using? > > -- > 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.
