Closed
Bug 1161491
Opened 10 years ago
Closed 10 years ago
schedulePreciseGC should use the normal GC triggering mechanisms
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla40
| Tracking | Status | |
|---|---|---|
| firefox40 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(1 file)
|
1.10 KB,
patch
|
mccr8
:
review+
|
Details | Diff | Splinter Review |
No description provided.
|
Assignee | |
Comment 1•10 years ago
|
||
Crossing fingers this would behave ok.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e098df958851
Attachment #8601426 -
Flags: review?(continuation)
|
|
Assignee | |
Comment 2•10 years ago
|
||
I don't see test failures on the few tests which use schedulePreciseGC or SpecialPowers.exactGC (which internally uses schedulePreciseGC).
|
||
Comment 3•10 years ago
|
||
Comment on attachment 8601426 [details] [diff] [review]
v1
Review of attachment 8601426 [details] [diff] [review]:
-----------------------------------------------------------------
Weird bit of code.
Attachment #8601426 -
Flags: review?(continuation) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox40:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•