Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1135850
Regression
No
Crash on Unity::SurfaceObserver::InitAPIObserver on stopping Play mode when using Holographic Emulation in Editor
How to reproduce:
1. Open the attached Unity project
2. Open the "Scene1" scene
3. In the Menu bar, open "XR/Holographic Emulation" window
4. Make sure "Emulation Mode" is set to "Simulate in Editor"
5. Enter Play mode
6. Wait for "Scene2" to get loaded
7. In the Console, observe dozens of "MissingReferenceException: The object of type 'Transform' has been destroyed but you are still trying to access it." errors
8. Stop the Play mode
-- Editor crash
Reproducible with - 2018.3.0b1, 2018.3.9f1, 2019.1.0a1, 2019.1.0b7, 2019.2.0a8
Stack trace:
(Unity) Unity::SurfaceObserver::InitAPIObserver
(Unity) Unity::SurfaceObserver::SetVolumeAsAxisAlignedBox
(Unity) SurfaceObserver_CUSTOM_SetVolumeAsAxisAlignedBox_Injected
(Mono JIT Code) (wrapper managed-to-native) UnityEngine.XR.WSA.SurfaceObserver:SetVolumeAsAxisAlignedBox_Injected (UnityEngine.XR.WSA.SurfaceObserver,UnityEngine.Vector3&,UnityEngine.Vector3&)
(Mono JIT Code) UnityEngine.XR.WSA.SurfaceObserver:SetVolumeAsAxisAlignedBox (UnityEngine.Vector3,UnityEngine.Vector3)
<...>
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (2019.2.X):
We are no longer updating 2019.2. If this is still an issue for you in 2019.3 or greater, please re-submit your bug.