Open Bug 1627953 Opened 5 years ago Updated 1 year ago

about:support doesn't report/show separate Remote Data Decoder (RDD) process in "Remote Processes" section

Categories

(Core :: Audio/Video: Playback, defect, P3)

Product:
Core
Component:
Audio/Video: Playback
Version:
65 Branch
Platform:
Desktop
All
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr68 --- affected
firefox74 --- affected
firefox75 --- affected
firefox76 --- affected
firefox77 --- affected

People

(Reporter: Virtual, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: nightly-community, reproducible, Whiteboard: [media-rdd])

Bug #1471535 implanted separate Remote Data Decoder (RDD) process controlled by "media.rdd-process.enabled" preference in about:config, and bug #1514874 enabled Remote Data Decoder (RDD) process starting only on-demand.

STR:

  1. Play some movie on some streaming website page to make sure Remote Data Decoder (RDD) process will spawn/start
  2. Open about:support
    and see that it doesn't report/show separate Remote Data Decoder (RDD) process in "Remote Processes" section.
Has Regression Range: --- → irrelevant
Has STR: --- → yes

Dan, do you know how we should go about addressing this?

Flags: needinfo?(dminor)
Priority: -- → P3
Whiteboard: [media-rdd]
OS: Windows 7 → All
Hardware: x86_64 → Desktop

FYI - Similar bug but about separate socket process was fixed recently in bug #1568028.

Flags: needinfo?(dminor)

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

I see the RDD process in about:support under Remote Processes. Does that mean this has been fixed?

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