Last Comment Bug 795686 - Lecture video player won't work in Firefox, does in Chrome
: Lecture video player won't work in Firefox, does in Chrome
Status: NEW
:
Product: Core
Classification: Components
Component: Audio/Video: Playback (show other bugs)
: Trunk
: All All
: -- normal with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-30 01:10 PDT by Andreas Kloeckner
Modified: 2016-02-04 19:52 PST (History)
9 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Andreas Kloeckner 2012-09-30 01:10:38 PDT
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 Iceweasel/17.0a2
Build ID: 20120928042009

Steps to reproduce:

I wrote a somewhat complex HTML5 video app that plays two video streams side-by-side (in this case, a screencast and a lecture video):

http://www.cims.nyu.edu/~kloeckner/hpc12-video/upload/html/player.html?descriptor=metadata/2012-09-05.json


Actual results:

The page works perfectly in Chrome, but dies in Firefox by not noticing that videos have finished seeking (i.e. not firing the corresponding events, as is evident from the debug log on the page). It does work fine in Firefox when run off a local webserver on my hard drive. Poking around with Firebug shows that Firefox does wonky things on the network--trying to download the entire video, for instance.


Expected results:

The page should have worked as well as it does in Chrome.
Comment 1 Loic 2012-10-03 15:11:58 PDT
Does it work normally in previous versions like FF14 or 15?
Comment 2 Andreas Kloeckner 2012-10-04 09:13:51 PDT
Based on a quick test, FF15 seems to behave no better than FF17.
Comment 3 Andreas Kloeckner 2013-08-28 12:39:09 PDT
FF23.0.1 is still unhappy.
Comment 4 Loic 2013-08-28 15:08:55 PDT
Is it possible to attach a reduced testcase showing the issue?
Comment 5 Andreas Kloeckner 2013-09-16 16:16:38 PDT
Attaching won't work because of large media files. Also, there seems to be a timing component to this, since everything works fine if I serve the content from my local machine.

For what it's worth, I've made a reduced version of the player that shows the same issue:
http://tiker.net/inteq13/html/player-simple.html
Comment 6 cajbir (:cajbir) 2013-09-16 20:19:35 PDT
(In reply to Andreas Kloeckner from comment #5)
> For what it's worth, I've made a reduced version of the player that shows
> the same issue:
> http://tiker.net/inteq13/html/player-simple.html

This example seems to work for me on a nightly build on Linux. What should I be seeing in failure?
Comment 7 Andreas Kloeckner 2013-09-16 21:39:25 PDT
In the debug window that pops up, you should at some point see "new state: paused", as you do in Chrome. Firefox never gets to this state for me. On FF23, I see a hang on "Stream {left,right}-audio loading media...".
Comment 8 cajbir (:cajbir) 2013-09-16 21:42:56 PDT
(In reply to Andreas Kloeckner from comment #7)
> In the debug window that pops up, you should at some point see "new state:
> paused", as you do in Chrome. Firefox never gets to this state for me. On
> FF23, I see a hang on "Stream {left,right}-audio loading media...".

I see it show "new state: paused" and then the debug window disappears. Is this what is supposed to happen?
Comment 9 Andreas Kloeckner 2013-09-16 21:58:39 PDT
Yes, that's the desired behavior--it means the streams have finished buffering.
Comment 10 Andreas Kloeckner 2013-09-16 22:28:56 PDT
Just tried a nightly (26.0a2). The hang persists for me. Note that this appears to have something to do with connection speed--see my comment above on how things work well for me when using a local HTTP server. I'm on a 3Mbps cable line.
Comment 11 Loic 2013-09-17 05:15:43 PDT
The testcase works erratically on my FF23, I need to reload the page 4 or 5 times.
Comment 12 Andreas Kloeckner 2013-09-25 08:55:26 PDT
I've observed that hitting the "seek to start" button in the full-scale player will usually fix things in FF23.
Comment 13 Chris Peterson [:cpeterson] 2014-02-21 18:01:13 PST
Andreas: can you still reproduce these video problems? I tested in Firefox 27, Aurora 29, and Nightly 30. The video seems to load (and then I can click play) in Nightly 30. In Firefox 27 and Aurora 29 the video looks like it is stuck in the loading state, but if I click ahead in the video timeline, then the video seems to load as expected.

Maybe this is race condition related to order in which video events are delivered to the content? Unfortunately, the http://www.cims.nyu.edu/ server itself kept crashing ("Service unavailable!") when I was testing these videos.
Comment 14 Andreas Kloeckner 2014-02-22 10:26:40 PST
Still an issue for me with Firefox 27--stuck on loading. Haven't tried the nightly.
Comment 15 Chris Pearce (:cpearce) 2014-02-23 13:34:33 PST
Nightly almost works for me.

If I load the video directly from http://www.cims.nyu.edu/~kloeckner/hpc12-video/upload/video/2012-09-05-room.webm it works fine, so the server seems to have enough bandwidth. But in Nightly on Windows the page loads up to the seeking state, but playback the video playback never starts when I load the page itself.

If I load right click and opt to show controls I can start playback using the in built controls. The page must be expecting us to fire an event...

Andreas: You know your own code much better than we do, it would be great if you could track down the behaviour difference between Chrome and Firefox that's causing your video player to not start playback. Maybe start by looking at what event your player is waiting on to start playback?
Comment 16 Andreas Kloeckner 2014-02-23 17:45:51 PST
The code waits for a can_play event, then executes a seek and waits for a seek_complete. The seek_complete usually doesn't arrive.
Comment 17 Anthony Jones (:kentuckyfriedtakahe, :k17e) 2016-02-04 19:34:40 PST
WFM on Mac OSX. Is this still reproducible?
Comment 18 Andreas Kloeckner 2016-02-04 19:52:47 PST
Still broken on Firefox 43 in Linux.

Note You need to log in before you can comment on or make changes to this bug.