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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (2018.3.X):
To be fixed by future mono update. Cause was invalid user data, fortunately this can be worked around.