Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
WorldAnchorManager causes WinRTScriptingObjectWrapper crash in Debug Mode
See original GitHub issueUsing the HoloLens, the call to GetAsync() in WorldAnchorManager::Awake() never returns. A breakpoint on line 65 is hit, then the app crashes. Runs fine in Release mode.
WinRTScriptingObjectWrapper::InternalAddRef Reference Count cannot be zero (Filename: C:\buildslave\unity\build\Runtime/ScriptingBackend/DotNet/ScriptingApi_DotNet.cpp Line: 661) The program '[4144] test8.exe' has exited with code -2147483645 (0x80000003).
We can replicate this on PCs with VS2017 Enterprise and Community, with Unity 5.6, and on two separate HoloLens devices.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Updated. The same result.
Just see this topic: https://forums.hololens.com/discussion/7203/vs2017-u5-6-crash-winrtscriptingobjectwrapper-internaladdref-reference-count-cannot-be-zero
Have the same problem with VS2017, Unity 5.60f3 and Hololens