This is a fork of issue 800673.

We migrated the video_VideoDecodeMemoryUsage test from dropped memory_stats API to new, but private python tracing APIs temporarily to get the test running. However, using these APIs is discouraged and we should again migrate to something else. (See the discussion on http://crosreview.com/858641 for details.)

Unfortunately, there doesn't seem to be any good alternative that would work with our testing method. This means that to get the test implemented properly, we need to work with Chromium team and either:
 - agree on a set of APIs for Chromium OS tests to use,
 - reconsider our testing method, e.g. it might be possible to turn the test into a Chromium benchmark.