Bug 142089

Summary: MediaSource should be suspendable when closed
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: MediaAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: buildbot, jer.noble, kling, koivisto, rniwa
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 142108    
Attachments:
Description Flags
Patch
none
Archive of layout-test-results from ews100 for mac-mavericks
none
Patch none

Chris Dumez
Reported 2015-02-27 10:38:44 PST
MediaSource should be suspendable when closed to increase to likelihood of pages using MediaSource to enter the PageCache. Radar: <rdar://problem/19923085>
Attachments
Patch (11.57 KB, patch)
2015-02-27 10:43 PST, Chris Dumez
no flags
Archive of layout-test-results from ews100 for mac-mavericks (602.52 KB, application/zip)
2015-02-27 11:25 PST, Build Bot
no flags
Patch (14.48 KB, patch)
2015-02-27 11:32 PST, Chris Dumez
no flags
Chris Dumez
Comment 1 2015-02-27 10:43:40 PST
Build Bot
Comment 2 2015-02-27 11:25:24 PST
Comment on attachment 247520 [details] Patch Attachment 247520 [details] did not pass mac-ews (mac): Output: http://webkit-queues.appspot.com/results/5563624995160064 New failing tests: fast/history/page-cache-media-source-opened.html fast/history/page-cache-media-source-closed.html fast/history/page-cache-media-source-closed-2.html
Build Bot
Comment 3 2015-02-27 11:25:28 PST
Created attachment 247526 [details] Archive of layout-test-results from ews100 for mac-mavericks The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: ews100 Port: mac-mavericks Platform: Mac OS X 10.9.5
Chris Dumez
Comment 4 2015-02-27 11:32:25 PST
Chris Dumez
Comment 5 2015-02-27 13:18:56 PST
Comment on attachment 247527 [details] Patch Clearing flags on attachment: 247527 Committed r180774: <http://trac.webkit.org/changeset/180774>
Chris Dumez
Comment 6 2015-02-27 13:19:01 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.