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
addAnchorPointUsingHitTestResultAsync kicks an exception.
call stack with a bunch of printf:
Frame is destroyed before being used for adding an anchor.
This is not an issue until the allocator returns the same allocated pointer. When the pointer is different (an allocation occured in the meantime), then the pointer is invalid. memory is cleared to zero after deallocation.
Investigations:
drawFrame happens in dtor for frame. Keeping a smartpointer will make rendering stutter for a few frames.
is it possible to attach System::Session::Frame to an object and not destroy/create every frame?
I've spent more hours today and keep same memory allocation for session::frame doesn't help.
Next try: keep a smart pointer on the session frame. As rendering code is in its destructor, there will be added latency and frozen frames. I think it's possible to fix that with a more explicit method call instead of rendering code in the destructor.
forum thread https://forum.babylonjs.com/t/babylonreactnative-throws-exception-when-adding-anchor/50716/13
addAnchorPointUsingHitTestResultAsync
kicks an exception.call stack with a bunch of printf:
Frame is destroyed before being used for adding an anchor.
This is not an issue until the allocator returns the same allocated pointer. When the pointer is different (an allocation occured in the meantime), then the pointer is invalid. memory is cleared to zero after deallocation.
Investigations:
BabylonNative/Plugins/NativeXr/Source/NativeXr.cpp
Line 1737 in 59798a7
XRPlane
as well.The text was updated successfully, but these errors were encountered: