Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f2
Issue ID
1037275
Regression
No
Crash on StreamedBinaryWrite<0>::Transfer<Vector3f> while compiling script in Playmode
How to reproduce:
1. Open the attached project
2. Open the "default" scene
3. Press Play
4. Double click on any galaxy
5. Double click on any solar system
6. Holding RMB navigate the view so the orbit lane is visible (white line around)
7. Double click on a planet (should be on the orbit lane, if there is none, double-click and choose another solar system)
8. Reimport PlanetManagement.cs script
9. Switch tabs between Console and Project
10. If Unity didn't crash already, repeat 8-9
Actual result: Unity crashes.
Reproducible with: 2018.3.0a1, 2018.2.0b7, 2018.1.4f1, 2017.4.5f1, 2018.2.3f1, 2017.1.4p1.
Note: 2018.3.0a1, 2018.2.0b7 doesn't crash, but freezes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment