Record scalar `device_hardware_decoding_support` on all platforms
Categories
(Core :: Audio/Video, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: alwu, Assigned: alwu)
References
(Regressed 1 open bug)
Details
Attachments
(6 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
2.70 KB,
text/plain
|
chutten
:
data-review+
|
Details |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
We want to extend this probe device_hardware_decoding_support on more platforms, which currently is only available on Windows. In addition, we would also like to report false
if user don't have the codec support.
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Depends on D208243
Assignee | ||
Comment 3•1 year ago
|
||
Depends on D208244
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Assignee | ||
Comment 4•1 year ago
|
||
Comment 5•1 year ago
|
||
Comment on attachment 9398262 [details]
data-review-request
DATA COLLECTION REVIEW RESPONSE:
Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?
Yes.
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes. This collection can be controlled through the product's preferences.
If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes, Alastor Wu and media-alerts@mozilla.com will be responsible.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, Technical.
Is the data collection request for default-on or default-off?
Default on for all channels.
Does the instrumentation include the addition of any new identifiers?
No.
Is the data collection covered by the existing Firefox privacy notice?
Yes.
Does the data collection use a third-party collection tool?
No.
Result: datareview+
Comment 7•1 year ago
|
||
Backed out for causing multiple failures @ toolkit/components/glean/api/src/private/boolean.rs
Backout link: https://hg.mozilla.org/integration/autoland/rev/f24ffc487097df9a1f47efcc366ebecf14b42b26
[ERROR firefox_on_glean::private::boolean] Unable to set boolean metric in non-main process. This operation will be ignored.
[task 2024-04-25T18:18:05.599Z] 18:18:05 INFO - GECKO(8304) | [4408] Hit MOZ_CRASH(Attempted to set boolean metric in non-main process, which is forbidden. This panics in automation.) at toolkit/components/glean/api/src/private/boolean.rs:61
[task 2024-04-25T18:18:05.657Z] 18:18:05 INFO - GECKO(8304) | [WARN webrender::device::gl] Cropping texture upload Box2D((0, 0), (0, 1)) to None
Comment 8•1 year ago
|
||
Assignee | ||
Comment 9•1 year ago
|
||
Assignee | ||
Comment 10•1 year ago
|
||
According to [1], currently we can only set a labeled boolean from the
chrome process, so we need to adjust our design to report result from
reporting from the GPU/RDD process to the chrome process.
Therefore, we have to always check HEVC first, and trim it later in
order to not to incorrectly support HEVC if the pref for HEVC is off.
Depends on D208715
Assignee | ||
Updated•1 year ago
|
Comment 11•1 year ago
|
||
Comment 12•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f1e2f8b3c62a
https://hg.mozilla.org/mozilla-central/rev/1b7a0986457b
https://hg.mozilla.org/mozilla-central/rev/6d4b0303e1aa
https://hg.mozilla.org/mozilla-central/rev/1a012d9139ca
https://hg.mozilla.org/mozilla-central/rev/8352f9721010
Description
•