Search Issue Tracker
Fixed in 2017.3.0f3
Votes
3
Found in
5.6.1f1
Issue ID
915065
Regression
Yes
[WSA] HoloLens application with MonoBehavior using OnMouseEnter crashes on startup in Debug config
Steps to reproduce:
1. Open the attached project (MouseCrash.zip)
2. Switch platform to Windows Store
3. Build for WSA Universal 10 (.NET backend), Build type - D3D, Target device - Hololens, Enable C# projects, Enable Copy references
4. Open Visual Studio solution
5. Deploy on local machine (DEBUG/x86)
6. Observe the crash
Expected result: Runs successfully and shows a white cube
Actual result: Prints the following to debug Output and the application exits.
Screen position out of view frustum (screen pos 0.000000, 0.000000) (Camera rect 0 0 1268 720)
(Filename: C:\buildslave\unity\build\Runtime/Camera/Camera.cpp Line: 2625)
The program '[3668] HoloToolkit-Unity.exe' has exited with code -2147483645 (0x80000003).
Note:
Not reproduced in Release config
Error is shown but an application does not crash in 5.5
Reproduced with: 5.6.1p1, 2017.1.0b7
Not reproduced with: 5.5.3p4
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Liviuss
Feb 03, 2018 19:31
Not resolved, still present in Unity 2017.3.p3 !
kmsuzanna
Aug 26, 2017 18:45
Any update on this?
psimon1
Jul 12, 2017 19:41
I am getting the same error with my HoloLens build. It is preventing me from debugging. It also shows up in the release version in the sense that Unity doesn't show the splash screen but jumps directly into the application. Any ideas of when this might be fixed? A patch to Unity 5.6.2f1 would be appreciated as we are not yet ready to move to 2017