Closed Bug 1841952 Opened 11 months ago Closed 11 months ago

Audio can still be decoded on tab process even after bug 1835804

Categories

(Core :: Audio/Video, defect, P2)

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: gerard-majax, Assigned: gerard-majax)

References

(Blocks 1 open bug)

Details

Attachments

(1 obsolete file)

In bug 1835804 we landed blockage of audio decoding on the tab process, which proved to hit some case which we fixed (bug 1839852, bug 1840371), but telemetry currently shows builds with the changes from bug 1835804, the preference not set to false and yet still reporting audio decoding of at least AAC, FLAC and Opus being done from Tab process, on all platforms.

Assignee: nobody → lissyx+mozillians
Attachment #9342578 - Attachment description: WIP: Bug 1841952 - Enforce more non utility audio decoder checking → Bug 1841952 - Enforce more non utility audio decoder checking r?alwu!
Depends on: 1844281

The severity field is not set for this bug.
:jimm, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies)
Severity: -- → S2
Priority: -- → P2

After a few days of running bug 1844281 landed on nightly:

  • we have no more report on Windows and macOS
  • we have two clients still reporting wrongful process name tab on linux. They seem to share the following: browser search region changed to PL, AMD G-T56N CPU, 3546MB of RAM and Linux 5.10.181.

(In reply to :gerard-majax [PTO 01/08/2023-10/09/2023] from comment #3)

After a few days of running bug 1844281 landed on nightly:

  • we have no more report on Windows and macOS
  • we have two clients still reporting wrongful process name tab on linux. They seem to share the following: browser search region changed to PL, AMD G-T56N CPU, 3546MB of RAM and Linux 5.10.181.

This was a bug in the dashboard:

  • there can be up to 3 prefs set, dashboard would only show the first one
  • those clients after verification of the raw data sets rdd-disabled, utility-disabled and allow-non-utility, in this order.

So in the reporting it would show only as rdd-disabled while we have allow-non-utility that explains the behavior.

Attachment #9342578 - Attachment is obsolete: true

We will re-open if telemetry shows real data supporting this.

Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: