[Bug] Fragments session does not load correctly, need to preload each fragment

[groolot]

• Open Stage Control version (or commit if built from sources) 1.12.0

• Operating system Debian GNU/Linux unstable, Firefox 96.0, Chromium 97.0.4692.71

• Open Stage Control options N/A

• Client type (built-in or external browser) and version Built-in

• Session file (can be uploaded after adding the .txt extension) end fragment chainsaw-gui-global-instrument-mixer.json.txt mixers fragment with 4 instances of chainsaw-gui-global-instrument-mixer chainsaw-gui-global-mixer.json.txt FX chain fragment chainsaw-gui-track-chain-fx.json.txt Particle fragment with an instance of chainsaw-gui-track-chain-fx.json chainsaw-gui-particletrack.json.txt Looper fragment with an instance of chainsaw-gui-track-chain-fx.json chainsaw-gui-loopertrack.json.txt Main with an instance of chainsaw-gui-loopertrack.json and chainsaw-gui-particletrack.json and chainsaw-gui-track-chain-fx.json chainsaw-gui.json.txt

Problem

When I try to load a global session with encapsulated fragments (nested) client enters in a kind of endless loop which is unfortunately not debugable within JavaScript console. But, if I preload each fragment before it is loaded by an encapsulator, everything is fine and the UI is fluid as beer in a dry throat.

[groolot]

https://user-images.githubusercontent.com/632571/149843384-53636b07-7383-4879-a604-a78b6d2e3562.mp4

[jean-emmanuel]

Found and fixed with f419ac8b, a nasty bug indeed !

[groolot]

Still have the same behaviour :(

[jean-emmanuel]

If you run a packaged v1.14.0 before pulling the latest commits you may encounter a caching issue, please pull and run npm run build again, I bumped the version number (it is used to determine the cache validity).

[groolot]

ok, the latest 291eb669 fixes the bug! great job!