Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.2.0b1
Issue ID
923422
Regression
No
Crash on Unity close when calling XRSettings.LoadDeviceByName with non-existent device name
To reproduce:
1. Open attached project;
2. Open "test" scene;
3. Enter play mode;
4. Exit play mode;
5. Repeat steps 3 and 4 until error "Assertion failed: VREyeTextureManager already had a texture." is thrown in the Console;
6. Exit Unity.
Expected result: no crash.
Actual result: Unity crashes on close when calling XRSettings.LoadDeviceByName with non-existent device name
Reproduced on versions: 5.5.4p1, 5.6.2f1, 2017.1.0b10, 2017.2.0b1.
Verified on: 2017.2.0b3 (4c2ac554540c).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- AsyncReadManager.GetFileInfo fails to get files when they were created during runtime.
- UI elements are not visible on certain X-axis positions when the rotation of the Y-axis is 90 (or -90) degrees
- Crash on __pthread_kill when initializing Vuplex WebView while entering the Play Mode
- Crash on FindSurface when adding a custom Renderer Feature to a 2D Renderer Data Asset
- [Android] [Vulkan] [UI Toolkit] Application crashes when the device is rotated when it has UI Toolkit TextField on Vulkan devices
Add comment