Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0a6
2018.3.0f2
2019.1.0a1
Issue ID
1110925
Regression
Yes
[XR] Editor crashes at VRDeviceHoloLens::BeginRenderingToDeviceGfxThread when simulating XR in Editor
Steps to reproduce:
1. Create a new project in 2018.2
2. Switch platform to UWP
3. Enable XR feature and in the Holographic window set "Emulation Mode" to "Simulate in Editor"
4. Save scene
5. Upgrade project to 2018.3 or 2019.1
6. Check if "Emulation Mode" is set to "Simulate in Editor"
7. Enter play mode
Results: On entering play mode Unity editor crashes
Reproduced with: 2019.1.0a13, 2018.3.1f1
Not reproducible with: 2018.3.0a5
Regression introduced in: 2018.3.0a6
========== OUTPUTTING STACK TRACE ==================
0x00007FF692B8BEB4 (Unity) VRDeviceHoloLens::BeginRenderingToDeviceGfxThread
0x00007FF692B8E93F (Unity) HoloLensEventGfxThreadCallback
0x00007FF692B25EAE (Unity) VRDevice::SendVRDeviceEvent
0x00007FF6932A90C0 (Unity) GfxDevice::SendVRDeviceEvent
0x00007FF693D1B977 (Unity) GfxDeviceWorker::RunCommand
0x00007FF693D1D4BB (Unity) GfxDeviceWorker::RunExt
0x00007FF693D1D885 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF6948B7287 (Unity) Thread::RunThreadWrapper
0x00007FFC49A27E94 (KERNEL32) BaseThreadInitThunk
0x00007FFC4C3DA251 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment