RESOLVED FIXED140974
REGRESSION (OS X 10.10.2): media/track/track-in-band-style.html frequently times out
https://bugs.webkit.org/show_bug.cgi?id=140974
Summary REGRESSION (OS X 10.10.2): media/track/track-in-band-style.html frequently ti...
Alexey Proskuryakov
Reported 2015-01-27 18:33:02 PST
media/track/track-in-band-style.html has started to time out about 50% of runs on debug WebKit1 and WebKit2 after upgrading the bots from OS X 10.0 to 10.10.2.
Attachments
Proposed patch. (4.59 KB, patch)
2015-01-29 10:57 PST, Eric Carlson
no flags
Updated patch. (5.40 KB, patch)
2015-01-29 11:11 PST, Eric Carlson
no flags
Radar WebKit Bug Importer
Comment 1 2015-01-27 18:33:29 PST
Alexey Proskuryakov
Comment 2 2015-01-27 18:38:15 PST
+CONSOLE MESSAGE: line 83: No text track cue with display id '-webkit-media-text-track-display' is currently visible +FAIL: Timed out waiting for notifyDone to be called Added a test expectation in <http://trac.webkit.org/r179237>.
Eric Carlson
Comment 3 2015-01-29 10:54:09 PST
This test plays ~1.5 seconds of a video with internal cues, seeks back to 0.3, and checks the style of the cue that should be visible at that time. When it fails, there isn't a visible cue because the media engine hasn't delivered a cue for that time, I believe because of startup latency.
Eric Carlson
Comment 4 2015-01-29 10:57:46 PST
Created attachment 245632 [details] Proposed patch. Introduce a brief pause between receiving the 'seemed' event and checking caption style to allow for media engine latency.
Eric Carlson
Comment 5 2015-01-29 11:11:41 PST
Created attachment 245634 [details] Updated patch.
Brent Fulgham
Comment 6 2015-01-29 15:03:40 PST
Comment on attachment 245634 [details] Updated patch. r = me
WebKit Commit Bot
Comment 7 2015-01-29 16:02:54 PST
Comment on attachment 245634 [details] Updated patch. Clearing flags on attachment: 245634 Committed r179377: <http://trac.webkit.org/changeset/179377>
WebKit Commit Bot
Comment 8 2015-01-29 16:02:59 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.