Comment 5 for bug 1417258

Justin recently investigated the ebay ad problem and we have a few theories here:

1. The high cpu usage is due to a highdef video format that is pushing the limits of what our HW can support. However, trying various user-agent strings for higher-end or lower-end devices did not change the type of video that was sent. So we can infer that the video we are sent is the one meant for our class of devices.

2. The high cpu usage is due to a switch of Youtube to using by default a new MediaSource construct. In particular, this involves demuxing the stream in the webview, in javascript. That may explain the higher cpu usage, causing the dropped frames. However, since that does not happen on Android, it would highlight a performance problem in our port the chrome engine. If the difference is mostly the js demuxing, that would indicate a v8 engine performance problem. Or maybe the fact that once processed the stream is sent via JS to a construct (the video frame) with a higher penalty than on other platforms.

3. This behavior is limited to Youtbe, and other video sites like Vimeo or Dailymotion seem to work fine for all of the popular video we have tested.