Closed
Bug 1545120
Opened 5 years ago
Closed 5 years ago
nsTimerImpl does not really need mCallbackDuringFire
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla68
People
(Reporter: bwc, Assigned: bwc)
Details
Attachments
(2 files)
It does not seem that the extra complexity to avoid refcount manipulation (by swapping) is worth it here. mCallbackDuringFire really ought to be a stack copy of mCallback.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → docfaraday
Assignee | ||
Comment 2•5 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=db4bbacc59aa030ecc060a7f3f73227dd074713d
Pushed by bcampen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bd62ad8bf26d Simplify this callback management stuff a little. r=froydnj
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Assignee | ||
Comment 5•5 years ago
|
||
Comment 6•5 years ago
|
||
bugherder uplift |
status-firefox67:
--- → fixed
Comment 7•5 years ago
|
||
bugherder uplift |
status-firefox-esr60:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•