Some users reported that but I can't reproduce it. Here is the code of the input component; https://gist.github.com/azer/87e6919fc24ad08839e01b1ee3158b4...

It depends on where your prop is coming from - at a guess I assume you're passing the value up the chain to some ancestor who is doing a setState. This'll cause the entire tree to re-render, including this component, and will cause a lockup if you're editing while this happens.

You can probably resolve this by implementing a shouldComponentUpdate here, or just debounce change handler.

You need to debounce