Virtual Time* works well for simple sites, but there are a number of sites where it doesn't work properly notably youtube.
General problems include: Virtual time incorrectly advancing while asynchronous operations such as dom storage lookups are in flight. The media stack may be issuing network requests which the VebViewScheduler isn't aware of. Finally the begin frame source isn't currently synchronised to virtual time without an eternal script issuing devtools commands.
We should try and fix all of these to make virtual time production ready.
* https://docs.google.com/document/d/1y9KDT_ZEzT7pBeY6uzVt1dgKlwc1OB_vY4NZO1zBQmo/edit
Comment 1 by alexclarke@chromium.org
, Oct 24 2017