Closed
Bug 1371376
Opened 7 years ago
Closed 7 years ago
Improvements to mscom smart pointers
Categories
(Core :: Disability Access APIs, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: bugzilla, Assigned: bugzilla)
References
Details
Attachments
(1 file, 1 obsolete file)
5.64 KB,
patch
|
jimm
:
review+
|
Details | Diff | Splinter Review |
It occurred to me that the mscom smart pointers are not as performant as they could be, because EnsureMTA always executes work on the MTA thread synchronously. A destruction operation doesn't really need to be synchronous, so we should make EnsureMTA support asynchronous operations and modify the mscom smart pointers to use it.
Assignee | ||
Comment 1•7 years ago
|
||
This patch also adds a new pointer type that does a delete in the MTA instead of a Release().
Attachment #8875857 -
Flags: review?(jmathies)
Assignee | ||
Comment 2•7 years ago
|
||
Attachment #8875857 -
Attachment is obsolete: true
Attachment #8875857 -
Flags: review?(jmathies)
Attachment #8875862 -
Flags: review?(jmathies)
Updated•7 years ago
|
Attachment #8875862 -
Flags: review?(jmathies) → review+
Assignee | ||
Comment 3•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/3fea90e94f1df641f540a3b62e42e171f9b9ee39 Bug 1371376: Make mscom smart pointers destroy their objects asynchronously; r=jimm
Assignee | ||
Comment 4•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=28b0d2d2216ae57ac42703f8f1feee61eedf708a
Assignee | ||
Comment 5•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/ee6c97bf9ca68e449662d9bba14ec83dc19753ba Bug 1371376: Fix static analysis errors; r=bustage
Comment 6•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3fea90e94f1d https://hg.mozilla.org/mozilla-central/rev/ee6c97bf9ca6
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•