Bug 50358 - REGRESSION: Video elements don't always show the first frame at page load
Summary: REGRESSION: Video elements don't always show the first frame at page load
Status: RESOLVED DUPLICATE of bug 57203
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Eric Carlson
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2010-12-01 16:22 PST by Simon Fraser (smfr)
Modified: 2022-02-12 18:40 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2010-12-01 16:22:33 PST 
On Mac, load up LayoutTests/compositing/geometry/video-opacity-overlay.html and reload the page a few times with Command-R. Every once in a while, the video is blank.

I think this is a recent regression.
Comment 1 Simon Fraser (smfr) 2010-12-01 16:22:57 PST 
<rdar://problem/8718678>
Comment 2 Simon Fraser (smfr) 2010-12-14 21:44:18 PST 
There are some pretty obvious differences in the movie notifications we get from QTKit in the success and failure cases. By adding some printfs, I saw:


Good
loadStateChanged (delayed 1)
loadStateChanged (delayed 0)
 updateStates: network state 2, ready state 2
setUpVideoRendering currentMode=0 preferredMode=3
acceleratedRenderingStateChanged
setUpVideoRendering currentMode=3 preferredMode=3
seeking to 0.000000 (metadata available 1)
timeChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4


Bad
loadStateChanged (delayed 1)
loadStateChanged (delayed 1)
loadStateChanged (delayed 0)
 updateStates: network state 2, ready state 2
setUpVideoRendering currentMode=0 preferredMode=3
acceleratedRenderingStateChanged
setUpVideoRendering currentMode=3 preferredMode=3
seeking to 0.000000 (metadata available 1)
timeChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
rateChanged (delayed 0)
 updateStates: network state 3, ready state 4
rateChanged (delayed 0)
 updateStates: network state 3, ready state 4
rateChanged (delayed 0)
 updateStates: network state 3, ready state 4
rateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
loadStateChanged (delayed 0)
 updateStates: network state 3, ready state 4
Comment 3 Brent Fulgham 2022-02-12 18:40:21 PST 

*** This bug has been marked as a duplicate of bug 57203 ***