Open
Bug 1089192
Opened 10 years ago
Updated 2 years ago
Expose ChromeOnly property on AudioNode for CPU usage
Categories
(Core :: Web Audio, defect, P3)
Tracking
()
NEW
People
(Reporter: jsantell, Unassigned)
References
Details
While in the spec, there doesn't seem to be much normative information regarding what this should be (just a Float between 0-100?)
In the mean time, this would be a great attribute to display and alert users to process-heavy nodes in the web audio developer tool.
Considerations:
* [ChromeOnly] API for now since it doesn't seem to be hammered out, or maybe expose it and be the trendsetters.
* Talking with padenot, this seems like it could potentially be costly if queried in the tool every ~1s or so, so maybe it'd just be used on one node at a time.
* If this is done, is there any global context information we can get from this work? Like a `AudioContext.prototype.cpuUsage` getter that's the aggregate of all the children AudioNodes' cpu usage?
Updated•9 years ago
|
Rank: 27
Priority: -- → P2
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•