So far the ui::GestureRecognizer is singleton, the instance is created for the first call of ui::GestureRecognizer::Get(). That leads to two instances on Mustash (since ash and browser will be in different processes). They'll need to synchronize with each other.
However, when both ash and browser are separated but reside within a single process, it comes back to a singleton instance, which is nice for the short term, but the synchronization problem goes invisible and can't be dealt with.
Maybe we may want to refactor the initialization of ui::GestureRecognizer, so that ash and browser will refer to different instances and let them communicate with each other, even when ash and browser runs in the same process.
Comment 1 by sky@chromium.org
, Aug 8