Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.2.0f1
Issue ID
953390
Regression
Yes
[Regression] 2017.2 Editor crashes with "System out of memory" error when connecting to 2017.1 Built Player
How to reproduce:
1. Open the provided "ReproPlayer" folder and download the attached Player
2. Launch the Player
3. Open the Editor (2017.2.0a4 or later 2017.2 version) and go to Window --> Profiler
4. Connect the Profiler to Player
Result: Editor crashes with "System out of memory" error
Regression introduced in - 2017.2.0a4
Reproducible when connecting 2017.1.1p3 built player to 2017.2.0a4
Not reproducible when connecting 2017.1.1p3 built player to 2017.2.0a3
Other tests:
Connecting 2017.1.1p3 built player to 2017.2.0f2 --> CRASH
Connecting 2017.1.1p3 built player to 2017.3.0b2 --> Not reproducible
Connecting 2017.2.0f2 built player to 2017.3.0b2 --> Not reproducible
Connecting 5.6.3p4 built player to 2017.2.0a4 --> Not reproducible
Connecting 2017.1.0a1 built player to 2017.2.0a4 --> CRASH (This indicates that the crash only happens when connecting 2017.1 player to the Profiler of 2017.2.0a4 and later)
Reproduced both on macOS Sierra 10.12.6 and Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
Add comment