Search Issue Tracker
Not Reproducible
Votes
3
Found in
2017.2.0b7
Issue ID
942257
Regression
No
Re-enabling version control and selecting top menu Assets>Version Control crashes at ValidateSubmenu
Steps to reproduce:
1. Setup perforce and create new project
2. Enable perforce VCS in editor
3. Reimport all
4. In top menu, go Assets>Version Control and notice that it opens up fine
5. Disable and re-enable perforce support
6. In top menu, go Assets>Version Control again
-Editor crashes at ValidateSubmenu
Reproduced with 2017.2.0b7, 2017.3.0a4, 2017.4.24
Not reproducible: 2018.3.11, 2019.1.0b9, 2019.2.0a10
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
Add comment