Bug 146818

Summary:	Implement extraMemoryCost() in MediaPlayerPrivateMediaStreamAVFObjC
Product:	WebKit	Reporter:	Matthew Daiter <mdaiter>
Component:	WebCore Misc.	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED INVALID
Severity:	Normal	CC:	bfulgham, eric.carlson, jonlee, mdaiter, webkit-bug-importer, webkit.review.bot
Priority:	P2	Keywords:	InRadar, PlatformOnly
Version:	528+ (Nightly build)
Hardware:	Unspecified
OS:	Unspecified
Bug Depends on:
Bug Blocks:	146746

Matthew Daiter

Reported 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.

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2015-07-09 16:34:56 PDT

<rdar://problem/21757280>

Matthew Daiter

Comment 2 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.

Jon Lee

Comment 3 2016-01-25 14:09:41 PST

This is not needed.

Note You need to log in before you can comment on or make changes to this bug.