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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment