Closed Bug 1866882 Opened 1 year ago Closed 1 year ago

Expose Default Agent registry mutex to JavaScript

Categories

(Toolkit :: Default Browser Agent, task)

task

Tracking

()

RESOLVED FIXED
122 Branch
Tracking Status
firefox122 --- fixed

People

(Reporter: nrishel, Assigned: nrishel)

References

Details

(Whiteboard: [fidedi])

Attachments

(4 files, 1 obsolete file)

We'll need to expose the Windows registry mutex to facilitate migration of control flow from the Default Agent C++ into JavaScript. As a bonus we can add some testing along the way.

Status: NEW → ASSIGNED
Whiteboard: [fidedi]
Blocks: 1793715
Blocks: 1867088
No longer blocks: 1793715
No longer blocks: 1867088
Blocks: 1867144

Depends on D195190

Attachment #9367765 - Attachment is obsolete: true
Pushed by nrishel@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c522c6c28406 Pre 1: Default Agent cleanup, simplifying includes and using appropriate console output. r=mhughes,nalexander https://hg.mozilla.org/integration/autoland/rev/6b647e88f727 Pre 2: Propogate error locking mutex from the Default Agent Background Task and Default Agent Proxy. r=nalexander,mhughes https://hg.mozilla.org/integration/autoland/rev/d8bd5e8a9e83 Part 1: Create XPCOM interface to manage Windows named mutexes. r=nalexander,mhughes https://hg.mozilla.org/integration/autoland/rev/3f446b63d45c Part 2: Add tests for `nsIWindowsMutex`. r=nalexander,mhughes
Regressions: 1869679
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: