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
currently I am working on a GL viewer using emscripten which should provide multiple canvases for visualizing heavy data (e.g. in 3D from different viewing directions). Obviously, it would advantagous if the heavy (big memory) data is only stored once and shared with the different canvases. After reading other posts (https://stackoverflow.com/questions/55921774/share-webassembly-memory-between-module-instances), it seems that instating one WebAssembly might be the best choice in order to avoid accidental overrides. However, SDL/emscripten currently requires one event loop per instance/module, so when generating different canvases from a single webassembly instance and only keeping one main event loop (e.g. of the first canvas), events for one canvas are missed. What should I do here?
I would like to avoid separate WebAssembly instances for individual canvases (which seems to be possible if setting the ID to canvas dynamically on mouseenter()), since here, each canvas requires its own "sandbox" memory, leading to latency and high memory footprint.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi list,
currently I am working on a GL viewer using emscripten which should provide multiple canvases for visualizing heavy data (e.g. in 3D from different viewing directions). Obviously, it would advantagous if the heavy (big memory) data is only stored once and shared with the different canvases. After reading other posts (https://stackoverflow.com/questions/55921774/share-webassembly-memory-between-module-instances), it seems that instating one WebAssembly might be the best choice in order to avoid accidental overrides. However, SDL/emscripten currently requires one event loop per instance/module, so when generating different canvases from a single webassembly instance and only keeping one main event loop (e.g. of the first canvas), events for one canvas are missed. What should I do here?
I would like to avoid separate WebAssembly instances for individual canvases (which seems to be possible if setting the ID to canvas dynamically on mouseenter()), since here, each canvas requires its own "sandbox" memory, leading to latency and high memory footprint.
Thanks, sophonet
Beta Was this translation helpful? Give feedback.
All reactions