Closed Bug 1760526 Opened 2 years ago Closed 2 years ago

Optional permission changes are not propagated to new processes

Categories

(WebExtensions :: General, defect, P1)

defect

Tracking

(firefox100 fixed)

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: zombie, Assigned: zombie)

References

Details

(Whiteboard: [addons-jira])

Attachments

(1 file)

When we grant an optional permission, we broadcast that to all existing child processes, but we never update the serialized values stored in Services.ppmm.sharedData.

Under e10s, it was easy for this to never have a real effect, we would quickly start the maximum number of content processes (between 1 and 8), and keep them alive till the browser is closed, never starting new ones. Also, the extension process where changes to permissions are most noticeable would have been already started, and never killed.

However with fission, most new tabs start a new process, it should be much more noticeable, and I'm really surprised we never got a bug report.

Blocks: 1745819
Whiteboard: [addons-jira]
Assignee: nobody → tomica
Status: NEW → ASSIGNED
Severity: -- → S2
Priority: -- → P1
Attachment #9268601 - Attachment description: Bug 1760526 - Save optional permission changes to sahredData for new processes r?robwu → Bug 1760526 - Save optional permission changes to sharedData for new processes r?robwu
No longer blocks: 1745819
See Also: → 1745819
Pushed by tjovanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4c9a0604dee6
Save optional permission changes to sharedData for new processes  r=robwu
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
See Also: → 1766822
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: