In r183467, checks have been added to avoid putting media resources from XHR requests in the disk cache, since they are likely specific to MSE streaming. But this does not check for Fetch requests, which can also be used for MSE streaming. This has been found by using Shaka Player on a low-end device. Playing high quality MSE content was pushing to the disk cache faster than the device could handle. Media data was accumulating in the the background IOQueue thread, and the NetworkProcess memory was constantly increasing. Recently, similar checks have been added for the MSE IPC overhead in r282003. Loïc found a few differences: - it supports ResourceLoadInfo::Type::XMLHTTPRequest and ResourceLoadInfo::Type::Fetch, but not ResourceLoadInfo::Type::Media - it has a different definition of isMediaMIMEType, which adds application/octet-stream to the audio/* and video/* we have in makeStoreDecision() Should we attempt to factorize these checks?
Created attachment 449846 [details] Patch
Comment on attachment 449846 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=449846&action=review Looks good > Source/WebKit/ChangeLog:23 > + No new tests (OOPS!). Can’t land a patch that still has this in it. Need to remove this line, and replace it with an explanation of why we are landing this patch without any tests. Might want to look back at the original XHR change to see how they wrote the test.
(In reply to Olivier Blin from comment #0) > Should we attempt to factorize these checks? Yes.
<rdar://problem/88288422>
Pull request: https://github.com/WebKit/WebKit/pull/24243