Search Issue Tracker
Fixed in 4.6.X
Votes
7
Found in
4.6.0b20
Issue ID
639857
Regression
Yes
Disabled input field crashes Unity when playing
To reproduce this bug:
1. Create a new project
2. Create an input field
3. Play
4. Stop
5. Disable input field in the hierarchy
6. Press play again
7. Crash
Comments (3)
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Fntastic_Ent
Feb 10, 2018 20:58
This bug has returned in Unity 2017.3.0f3
nventimiglia
Oct 20, 2014 20:24
http://forum.unity3d.com/threads/scene-becoming-corrupted-crash-bug.274884/#post-1815279
Hahahaag
Oct 17, 2014 21:54
Issue is caused by the combination of running the game and disabling the InputField (or it's parent) in the Editor, a Caret GameObject is created inside the Text component, and that cause the conflict when you hit Play.
I was able to do a quick "hacky" fix by extending the InputField class and using the OnEnable and OnDisable methods, combined with EditorApplication.update to check for the Caret GameObject, and removing when he appears in Editor mode. This method is not ideal, but it was the only way to fix this issue.