Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.1.2f1
Issue ID
1060651
Regression
No
Crash in "object_commands" when entering Playmode with VS Debugger attached
To reproduce:
1. Download the attached project and the data.zip
2. Play the "KombinatorObleku" scene
3. It will ask you for a data folder, create one
4. Exit play mode and overwrite the data folder with the data.zip contents
5. Using the Visual Studio open the "Synchronizer.cs" and put a breakpoint at line 306
6. Attach Visual Studio debugger to the Unity
7. Play the scene and switch back to Visual Studio
-- Unity crashes
Reproduced with: 2017.4.8f1, 2018.1.9f1, 2018.2.2f2, 2018.3.0a7
Notes:
- The editor is throwing an exception when playing the scene, however only crashes when the VS debugger is attached
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2018.3.X):
To be fixed by future mono update. Cause was invalid user data, fortunately this can be worked around.