Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
900694
Regression
Yes
Crash in "mono_class_vtable_full" when entering the playmode and accessing BaseInput component
How to reproduce:
1. Open the attached "SmallerReproProject' project
2. Open the "Sandbox" scene and enter playmode
Expected result: Playmode is entered
Actual result: Crash occurs
Notes:
1. Couldn't reproduce this with 5.5 version of Unity, since it didn't support the 9-slice Sprite rendering which was introduced in 5.6.0b3. And after commenting SpriteRenderer.size methods, the project just provides a lot of "NullReferenceException" errors, but stops crashing
2. Commenting 41st line in a BaseActionPlayerComponent.cs script seems to solve the crash. -> _input = _player.GetComponent<BaseInput>();
Reproducible with - 2017.1.0b1, 5.6.0p1, 5.6.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- [MacOS] AdvancedDropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
Add comment