Closed
Bug 1081732
Opened 10 years ago
Closed 8 years ago
Evaluate implementing flash.system.System.*Memory getters
Categories
(Firefox Graveyard :: Shumway, defect)
Firefox Graveyard
Shumway
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: till, Unassigned)
References
Details
Implementing these in the extension wouldn't be all that hard. At least for now, though, I doubt we want to do that: as long as we're running in the same process as all other content, this opens a side channel through which other sites can be attacked. That is exactly the reason why JS engines don't expose this information to content. The documentation for `flash.system.System.freeMemory` contains this gem: "Use this property to monitor garbage collection", so these are meant precisely for the use case we want to prevent. (Note that as of now, the Flash player might actually grant a vector for this kind of attack, depending on whether these numbers are accurate with the plugin running in its own process.) We might get away with implementing them once we have moved to an e10s process, but a careful analysis would have to be done first.
Updated•10 years ago
|
Blocks: shumway-1.0
Updated•9 years ago
|
Blocks: shumway-later
Comment 1•9 years ago
|
||
This bug does not need to block Shumway's 1.0 milestone for ads.
No longer blocks: shumway-1.0
Assignee | ||
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•