[BUG] Body tracking is offset when unmounting and remounting HMD in scenes using MRUK #130
Description
Unity version
6000.0.56f1
Meta XR Core SDK version
v83
Which OS are you using?
Windows 11
Where does the issue occur?
- In Unity Editor
- In Quest builds
Description
We are currently working on a Quest 3 Augmented Reality app for physical rehabilitation purposes. As such, we're using the Movement SDK to track the user's body movements and use those as gameplay input and to analyze player rehabilitation progress.
What we noticed over time is that when taking the headset off and putting it back on, some of the tracking data seemed incorrect. After turning on the Debug Draw Skeleton option on the MetaSourceDataProvider, we could see that in fact the tracked skeleton was no longer aligned with the user.
The camera rig and passthrough setup were all created using building blocks. The body tracking setup is derived from the StylizedCharacter. Adding the provided HMDRemountRestartTracking component did also not resolve the issue.
Through a process of elimination and starting in an empty project from scratch, we noticed that the behaviour did not appear when using the tracking on its own. It seemed stable and recovered fine after taking the HMD off and putting it back on. Only when adding the MRUK prefab to the scene did the issues start to appear again.
We are using MRUK to get info about the physical space and we're using the room mesh for environment and gameplay purposes. What we did notice however is that when we turn off Enable World Lock on the MRUK component, the body tracking issues would once again disappear. This would of course come with alignment issues between our physical space and the virtual objects placed in it, so is not a solution for us.
To illustrate the problem we made a recording. Unfortunately recording stops when taking the headset off, so there are two recordings rather than a continuous one, but this is from one continous "session".
Before taking off HMD: https://youtube.com/shorts/mTcvPNg1NYw
After remounting HMD, having moved: https://youtube.com/shorts/yf1qXeCFMhE
Trying to find cases similar to ours in earlier issues as well as on forums did not reveal anything. Perhaps there is an obvious resolution to the problem, in which case we'd love to know. Or if it's an actual bug, it would be great to see this resolved.
Steps to reproduce
We created a respository containing two scenes which help to illustrate the issue. You can find it here: https://github.com/bkevelham/meta-movement-sdk-mruk-bug
In it you will find two scenes:
BodyTrackingWithNoMRUK is the base setup of a camera rig with passthrough enabled, and includes the StylizedCharacter with a HMDRemountRestartTracking script attached. A build of this should normally reveal no significant issues.
BodyTrackingWithMRUK is the same scene, except with the MRUK prefab added. A build of this scene should exhibit the problems described before. Once inside the scene, verify that body tracking seems correct. Both the model in this case, as well as the debug skeleton, should appear correctly. Now take the headset off and, for example, rotate around 90 degrees, take a step forward, and remount the headset. You should notice once back in the app that the model and skeleton will no longer be aligned.
If however you disabled Enable World Lock on the MRUK prefab and rebuild, you will notice that as far as body tracking is concerned, the problems disappear once again.
If you wish to create the example from scratch, it suffices to add the following to an empty scene:
- Camera Rig building block
- Passthrough building block
- StylizedCharacter prefab
- MRUK prefab
Logs
02-05 14:49:45.093 25189 25189 V Unity : Context Type: GameActivity
02-05 14:49:45.098 25189 25213 I Unity : UnityApplication::CreateInstance
02-05 14:49:45.098 25189 25213 I Unity : GameActivity Package Version '3.0.5'
02-05 14:49:45.099 25189 25213 I Unity : Starting Game Loop
02-05 14:49:45.102 25189 25213 I Unity : Handle cmd APP_CMD_START(11)
02-05 14:49:45.106 25189 25213 I Unity : Handle cmd APP_CMD_RESUME(12)
02-05 14:49:45.139 25189 25213 I Unity : Handle cmd APP_CMD_GAINED_FOCUS(7)
02-05 14:49:45.139 25189 25213 I Unity : Handle cmd APP_CMD_LOST_FOCUS(8)
02-05 14:49:45.148 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:45.149 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:45.149 25189 25213 I Unity : Handle cmd APP_CMD_CONTENT_RECT_CHANGED(5)
02-05 14:49:45.151 25189 25213 I Unity : Handle cmd APP_CMD_INIT_WINDOW(1)
02-05 14:49:45.156 25189 25213 I Unity : MemoryManager: Using 'Dynamic Heap' Allocator.
02-05 14:49:45.210 25189 25213 I Unity : SystemInfo CPU = ARM64 FP ASIMD AES, Cores = 6, Memory = 7756mb
02-05 14:49:45.210 25189 25213 I Unity : SystemInfo ARM big.LITTLE configuration: 4 big (mask: 0x3c), 2 little (mask: 0x3)
02-05 14:49:45.210 25189 25213 I Unity : XR UsableCoreMask: 0x3f
02-05 14:49:45.210 25189 25213 I Unity : ApplicationInfo 'com.UnityTechnologies.com.unity.template.urpblank', Version '0.1.0', Min API Level '32', Target API Level '32'
02-05 14:49:45.210 25189 25213 I Unity : Built from '6000.0/staging' branch, Version '6000.0.56f1 (9c7b5e468860)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a', Stripping 'Enabled'
02-05 14:49:45.210 25189 25213 I Unity : Device Model 'Oculus Quest', OS 'Android OS 14 (API 34)'
02-05 14:49:45.563 25189 25213 I Unity : Company Name: Fondation Artanim
02-05 14:49:45.563 25189 25213 I Unity : Product Name: body-tracking-debug
02-05 14:49:45.565 25189 25213 D Unity : loading library OVRPlugin
02-05 14:49:46.059 25189 25213 I Unity : XRGeneral Settings awakening...
02-05 14:49:46.059 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.059 25189 25213 I Unity : UnityEngine.XR.Management.XRGeneralSettings:Awake()
02-05 14:49:46.059 25189 25213 I Unity :
02-05 14:49:46.302 25189 25213 I Unity : HasWindow = 1, HasFocus = 0
02-05 14:49:46.302 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_RESIZED(3)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_REDRAW_NEEDED(4)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_GAINED_FOCUS(7)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.303 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.472 25189 25213 D Unity : initOculus Java!
02-05 14:49:46.472 25189 25189 D Unity : Oculus UI thread done.
02-05 14:49:46.491 25189 25213 W Unity : MRUK Shared: Unable to bind OpenXR function
02-05 14:49:46.491 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.491 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:OnSharedLibLog(MrukLogLevel, Char*, UInt32)
02-05 14:49:46.491 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:InitializeSharedLibrary()
02-05 14:49:46.491 25189 25213 W Unity :
02-05 14:49:46.492 25189 25213 W Unity : MRUK Shared: Unable to bind OpenXR function
02-05 14:49:46.492 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:OnSharedLibLog(MrukLogLevel, Char*, UInt32)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:InitializeSharedLibrary()
02-05 14:49:46.492 25189 25213 W Unity :
02-05 14:49:46.492 25189 25213 W Unity : MRUK Shared: Unable to bind OpenXR function
02-05 14:49:46.492 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:OnSharedLibLog(MrukLogLevel, Char*, UInt32)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:InitializeSharedLibrary()
02-05 14:49:46.492 25189 25213 W Unity :
02-05 14:49:46.492 25189 25213 W Unity : MRUK Shared: Unable to bind OpenXR function
02-05 14:49:46.492 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:OnSharedLibLog(MrukLogLevel, Char*, UInt32)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:InitializeSharedLibrary()
02-05 14:49:46.492 25189 25213 W Unity :
02-05 14:49:46.492 25189 25213 W Unity : MRUK Shared: Unable to bind OpenXR function
02-05 14:49:46.492 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:OnSharedLibLog(MrukLogLevel, Char*, UInt32)
02-05 14:49:46.492 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:InitializeSharedLibrary()
02-05 14:49:46.492 25189 25213 W Unity :
02-05 14:49:46.569 25189 25213 I Unity : Unity v6000.0.56f1, Oculus Utilities v1.115.0, OVRPlugin v1.115.0, SDK v1.1.51.
02-05 14:49:46.569 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.569 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.569 25189 25213 I Unity :
02-05 14:49:46.570 25189 25213 I Unity : SystemHeadset Meta_Quest_3, API OpenXR
02-05 14:49:46.570 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.570 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.570 25189 25213 I Unity :
02-05 14:49:46.570 25189 25213 I Unity : OpenXR instance 0x2 session 0x50
02-05 14:49:46.570 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.570 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.570 25189 25213 I Unity :
02-05 14:49:46.572 25189 25213 I Unity : OVRPlugin.Media not initialized
02-05 14:49:46.572 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.572 25189 25213 I Unity : OVRManager:StaticInitializeMixedRealityCapture(OVRMixedRealityCaptureConfiguration)
02-05 14:49:46.572 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.572 25189 25213 I Unity :
02-05 14:49:46.582 25189 25213 I Unity : Current display frequency 90, available frequencies [72, 80, 90, 120]
02-05 14:49:46.582 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.582 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.582 25189 25213 I Unity :
02-05 14:49:46.587 25189 25213 W Unity : Local Dimming feature is not supported
02-05 14:49:46.587 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.587 25189 25213 W Unity : OVRManager:InitOVRManager()
02-05 14:49:46.587 25189 25213 W Unity :
02-05 14:49:46.589 25189 25213 I Unity : [OVRManager] Current hand skeleton version is OpenXR
02-05 14:49:46.589 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.589 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.589 25189 25213 I Unity :
02-05 14:49:46.589 25189 25213 I Unity : Oculus XR Runtime Settings:
02-05 14:49:46.589 25189 25213 I Unity : Depth Submission - False
02-05 14:49:46.589 25189 25213 I Unity : Foveated Rendering Method - FixedFoveatedRendering
02-05 14:49:46.589 25189 25213 I Unity : Optimize Buffer Discards - True
02-05 14:49:46.589 25189 25213 I Unity : Symmetric Projection - True
02-05 14:49:46.589 25189 25213 I Unity : Subsampled Layout - True
02-05 14:49:46.589 25189 25213 I Unity : Space Warp - False
02-05 14:49:46.589 25189 25213 I Unity : Late Latching - False
02-05 14:49:46.589 25189 25213 I Unity : Low Overhead Mode - True
02-05 14:49:46.589 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.589 25189 25213 I Unity : OVRManager:InitOVRManager()
02-05 14:49:46.589 25189 25213 I Unity :
02-05 14:49:46.618 25189 25213 I Unity : [OVRManager] OnApplicationPause(false)
02-05 14:49:46.618 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.618 25189 25213 I Unity :
02-05 14:49:46.618 25189 25213 I Unity : [OVRManager] OnApplicationFocus(true)
02-05 14:49:46.618 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.618 25189 25213 I Unity :
02-05 14:49:46.668 25189 25213 I Unity : [OVRManager] HMDAcquired event
02-05 14:49:46.668 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.668 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.668 25189 25213 I Unity :
02-05 14:49:46.668 25189 25213 I Unity : [OVRManager] HMDMounted event
02-05 14:49:46.668 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.668 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.668 25189 25213 I Unity :
02-05 14:49:46.669 25189 25213 I Unity : [OVRManager] VrFocusAcquired event
02-05 14:49:46.669 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.669 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.669 25189 25213 I Unity :
02-05 14:49:46.669 25189 25213 I Unity : [OVRManager] InputFocusLost event
02-05 14:49:46.669 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.669 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.669 25189 25213 I Unity :
02-05 14:49:46.671 25189 25213 I Unity : Recenter event detected
02-05 14:49:46.671 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.671 25189 25213 I Unity : OVRDisplay:Update()
02-05 14:49:46.671 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.671 25189 25213 I Unity :
02-05 14:49:46.675 25189 25213 W Unity : MRUK Shared: World Lock anchor handle is null
02-05 14:49:46.675 25189 25213 W Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.675 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:OnSharedLibLog(MrukLogLevel, Char*, UInt32)
02-05 14:49:46.675 25189 25213 W Unity : Meta.XR.MRUtilityKit.MRUK:Update()
02-05 14:49:46.675 25189 25213 W Unity :
02-05 14:49:46.678 25189 25213 I Unity : Unable to process a controller whose SampleRateHz is 0 now.
02-05 14:49:46.678 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.678 25189 25213 I Unity : OVRHapticsOutput:Process()
02-05 14:49:46.678 25189 25213 I Unity : OVRHaptics:Process()
02-05 14:49:46.678 25189 25213 I Unity : OVRManager:LateUpdate()
02-05 14:49:46.678 25189 25213 I Unity :
02-05 14:49:46.678 25189 25213 I Unity : Unable to process a controller whose SampleRateHz is 0 now.
02-05 14:49:46.678 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.678 25189 25213 I Unity : OVRHapticsOutput:Process()
02-05 14:49:46.678 25189 25213 I Unity : OVRHaptics:Process()
02-05 14:49:46.678 25189 25213 I Unity : OVRManager:LateUpdate()
02-05 14:49:46.678 25189 25213 I Unity :
02-05 14:49:46.798 25189 25213 I Unity : RenderGraph is now enabled.
02-05 14:49:46.798 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.798 25189 25213 I Unity : UnityEngine.Rendering.Universal.UniversalRenderPipeline:.ctor(UniversalRenderPipelineAsset)
02-05 14:49:46.798 25189 25213 I Unity : UnityEngine.Rendering.Universal.UniversalRenderPipelineAsset:CreatePipeline()
02-05 14:49:46.798 25189 25213 I Unity : UnityEngine.Rendering.RenderPipelineAsset:InternalCreatePipeline()
02-05 14:49:46.798 25189 25213 I Unity : UnityEngine.Rendering.RenderPipelineManager:TryPrepareRenderPipeline(RenderPipelineAsset)
02-05 14:49:46.798 25189 25213 I Unity : UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal(RenderPipelineAsset, IntPtr, Object)
02-05 14:49:46.798 25189 25213 I Unity :
02-05 14:49:46.872 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.872 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:46.945 25189 25213 I Unity : [OVRManager] InputFocusAcquired event
02-05 14:49:46.945 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.945 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.945 25189 25213 I Unity :
02-05 14:49:46.945 25189 25213 I Unity : [OVRManager] TrackingAcquired event
02-05 14:49:46.945 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:46.945 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:46.945 25189 25213 I Unity :
02-05 14:49:47.048 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:47.048 25189 25213 I Unity : Handle cmd APP_CMD_WINDOW_INSETS_CHANGED(17)
02-05 14:49:47.077 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.077 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.165 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.165 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.225 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.225 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.299 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.299 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.357 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.357 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.426 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.426 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.482 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.482 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.551 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.551 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.607 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.607 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.662 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.662 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.704 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.704 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.758 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.758 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.802 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.802 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.856 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.856 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.899 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.899 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.954 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.954 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:47.996 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:47.996 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.051 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.051 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.092 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.092 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.148 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.148 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.190 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.190 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.245 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.245 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.287 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.287 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.343 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.343 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.384 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.384 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.440 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.440 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.482 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.482 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.537 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.537 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.578 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.578 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.635 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.635 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.676 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.676 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.732 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.732 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.773 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.773 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.829 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.829 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.871 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.871 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.926 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.926 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:48.968 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:48.968 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.023 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.024 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.066 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.066 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.122 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.122 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.163 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.163 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.219 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.219 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.261 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.261 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.316 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.316 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.357 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.357 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.413 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.413 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.455 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.455 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.510 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.510 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.552 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.552 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.608 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.608 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.649 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.649 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.705 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.705 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.747 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.747 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.802 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.802 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.844 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.844 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.900 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.900 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.941 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.941 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:49.996 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:49.996 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:50.039 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:50.039 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:50.094 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:50.094 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:50.138 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:50.138 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:50.176 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:50.176 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:50.218 25189 25213 W Unity : Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
02-05 14:49:50.218 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:49:53.362 25189 25213 I Unity : [OVRManager] HMDUnmounted event
02-05 14:49:53.362 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:53.362 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:53.362 25189 25213 I Unity :
02-05 14:49:58.171 25189 25213 I Unity : [OVRManager] HMDMounted event
02-05 14:49:58.171 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:58.171 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:58.171 25189 25213 I Unity :
02-05 14:49:58.171 25189 25213 I Unity : Rebooting body tracking after HMD remounted. Stopping...
02-05 14:49:58.171 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:58.171 25189 25213 I Unity : Meta.XR.Movement.Utils.HMDRemountRestartTracking:HandleHMDMounted()
02-05 14:49:58.171 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:58.171 25189 25213 I Unity :
02-05 14:49:58.172 25189 25213 I Unity : Starting body tracking.
02-05 14:49:58.172 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:58.172 25189 25213 I Unity : Meta.XR.Movement.Utils.HMDRemountRestartTracking:HandleHMDMounted()
02-05 14:49:58.172 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:58.172 25189 25213 I Unity :
02-05 14:49:58.199 25189 25213 I Unity : Recenter event detected
02-05 14:49:58.199 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:58.199 25189 25213 I Unity : OVRDisplay:Update()
02-05 14:49:58.199 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:58.199 25189 25213 I Unity :
02-05 14:49:59.053 25189 25213 I Unity : Recenter event detected
02-05 14:49:59.053 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:49:59.053 25189 25213 I Unity : OVRDisplay:Update()
02-05 14:49:59.053 25189 25213 I Unity : OVRManager:Update()
02-05 14:49:59.053 25189 25213 I Unity :
02-05 14:50:00.496 25189 25213 I Unity : Recenter event detected
02-05 14:50:00.496 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:00.496 25189 25213 I Unity : OVRDisplay:Update()
02-05 14:50:00.496 25189 25213 I Unity : OVRManager:Update()
02-05 14:50:00.496 25189 25213 I Unity :
02-05 14:50:06.765 25189 25213 I Unity : Unable to process a controller whose SampleRateHz is 0 now.
02-05 14:50:06.765 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:06.765 25189 25213 I Unity : OVRHapticsOutput:Process()
02-05 14:50:06.765 25189 25213 I Unity : OVRHaptics:Process()
02-05 14:50:06.765 25189 25213 I Unity : OVRManager:LateUpdate()
02-05 14:50:06.765 25189 25213 I Unity :
02-05 14:50:06.765 25189 25213 I Unity : Unable to process a controller whose SampleRateHz is 0 now.
02-05 14:50:06.765 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:06.765 25189 25213 I Unity : OVRHapticsOutput:Process()
02-05 14:50:06.765 25189 25213 I Unity : OVRHaptics:Process()
02-05 14:50:06.765 25189 25213 I Unity : OVRManager:LateUpdate()
02-05 14:50:06.765 25189 25213 I Unity :
02-05 14:50:06.767 25189 25213 I Unity : Handle cmd APP_CMD_LOST_FOCUS(8)
02-05 14:50:06.768 25189 25213 I Unity : [OVRManager] OnApplicationFocus(false)
02-05 14:50:06.768 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:06.768 25189 25213 I Unity :
02-05 14:50:06.943 25189 25213 I Unity : [OVRManager] InputFocusLost event
02-05 14:50:06.943 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:06.943 25189 25213 I Unity : OVRManager:Update()
02-05 14:50:06.943 25189 25213 I Unity :
02-05 14:50:08.991 25189 25213 I Unity : Handle cmd APP_CMD_PAUSE(14)
02-05 14:50:09.098 25189 25213 I Unity : Recenter event detected
02-05 14:50:09.098 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:09.098 25189 25213 I Unity : OVRDisplay:Update()
02-05 14:50:09.098 25189 25213 I Unity : OVRManager:Update()
02-05 14:50:09.098 25189 25213 I Unity :
02-05 14:50:09.143 25189 25213 I Unity : [OVRManager] OnApplicationPause(true)
02-05 14:50:09.143 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:09.143 25189 25213 I Unity :
02-05 14:50:09.152 25189 25213 I Unity : Handle cmd APP_CMD_TERM_WINDOW(2)
02-05 14:50:09.165 25189 25213 I Unity : Handle cmd APP_CMD_STOP(15)
02-05 14:50:09.166 25189 25213 I Unity : Handle cmd APP_CMD_DESTROY(16)
02-05 14:50:09.166 25189 25213 I Unity : UnityApplication::DestroyInstance
02-05 14:50:09.167 25189 25213 I Unity : [OVRManager] OnApplicationQuit
02-05 14:50:09.167 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:09.167 25189 25213 I Unity :
02-05 14:50:09.272 25189 25213 I Unity : [OVRManager] OnDestroy
02-05 14:50:09.272 25189 25213 I Unity : UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
02-05 14:50:09.272 25189 25213 I Unity : OVRManager:OnDestroy()
02-05 14:50:09.272 25189 25213 I Unity :
02-05 14:50:09.359 25189 25213 W Unity : Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance
02-05 14:50:09.359 25189 25213 W Unity : To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
02-05 14:50:09.375 25189 25213 I Unity : Quitting process
Additional info
No response