Bug 146818 - Implement extraMemoryCost() in MediaPlayerPrivateMediaStreamAVFObjC
Summary: Implement extraMemoryCost() in MediaPlayerPrivateMediaStreamAVFObjC
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar, PlatformOnly
Depends on:
Blocks: 146746
  Show dependency treegraph
 
Reported: 2015-07-09 16:33 PDT by Matthew Daiter
Modified: 2016-01-25 14:09 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Daiter 2015-07-09 16:33:51 PDT
Need to implement this function inside of MediaPlayer's engine to make sure that the system can accurately calculate this.
Comment 1 Radar WebKit Bug Importer 2015-07-09 16:34:56 PDT
<rdar://problem/21757280>
Comment 2 Matthew Daiter 2015-08-05 11:28:27 PDT
What does this even mean in context? Like, I get that the Tracks could add in an extra amount of memory to the engine, but how do you estimate "extraMemoryCost" of an engine...?
Comparing it to itself with new added tracks?
MediaPlayerPrivateMediaSourceAVFObjC::extraMemoryCost() returns 0.
Comment 3 Jon Lee 2016-01-25 14:09:41 PST
This is not needed.