syntheticmagus

#821 discusses one possible way to address this, among other considerations.

Hi @HedwigAR, Thanks for a providing a repository! However, I'm currently not reproing the behavior you describe. For the first case, I don't see any unbounded memory growth; the app...

Thanks for the additional information! Based on this, I was able to get the first scenario to repro in Babylon Native proper, where I could see that there was something...

For whatever reason, VS memory profiling tools aren't working on the Babylon Native Playground app (snapshots spin forever and never become inspectable), but by futzing with refresh it looks like,...

May pertain to the following NDK bug: https://github.com/android/ndk/issues/1639

Affected by https://github.com/microsoft/arcana.cpp/pull/36.

We should try to get this to fall back into Babylon.js's default behaviors for browsers that don't support WebXR, since that should handle the situation gracefully from the JavaScript side...

Though slightly tangential, a change which might be worth pursuing at the same time as this would be to modify the `HitTest` API to make its mechanism a little more...

https://stackoverflow.com/questions/32894051/how-to-do-parallel-cmake-externalproject-builds#:~:text=When%20building%20a%20CMake%20project%20%28e.g.%20on%20Windows%29%2C,is%20not%20passed%20through%20to%20its%20build%20command. @chrisfromwork It looks like it's possible for people to do this for themselves at config time. Is that sufficient, or do we believe this should be integrated more deeply...

If this does end up being a plugin (lots of remaining investigation to figure out if that's the right answer), should it live in this repo? Or should that be...