Closed
Bug 1294563
Opened 9 years ago
Closed 9 years ago
Yield before compacting GC if we are incremental
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
mozilla52
People
(Reporter: terrence, Assigned: terrence)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file, 2 obsolete files)
|
1.67 KB,
patch
|
jonco
:
review+
gchang
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
This got broken when we added a finalize state. We're now yielding at the end of sweeping... right before the zero-length finalize slices instead of before the long compacting slices. Should be trivial to fix.
| Assignee | ||
Comment 1•9 years ago
|
||
I think this is probably not necessary because sweepZones should be relatively fast. Probably better to err on the size of low-latency though.
Attachment #8793046 -
Flags: review?(jcoppeard)
| Assignee | ||
Comment 2•9 years ago
|
||
Looks like we don't even visit the thing for sweeping, so the final shutdown crashes in the pre-barrier as we've already torn down the heap.
| Assignee | ||
Comment 3•9 years ago
|
||
Let's just take out all the GC primitives since the map is not managed by the GC.
Attachment #8793046 -
Attachment is obsolete: true
Attachment #8793046 -
Flags: review?(jcoppeard)
Attachment #8793121 -
Flags: review?(nicolas.b.pierron)
Comment 4•9 years ago
|
||
(In reply to Terrence Cole [:terrence] from comment #3)
The above looks like a fine patch but I think you meant to open a different bug for it.
Flags: needinfo?(terrence.d.cole)
Comment 5•9 years ago
|
||
Comment on attachment 8793121 [details] [diff] [review]
no_need_for_rekeyable_on_vmfunction-v1.diff
Review of attachment 8793121 [details] [diff] [review]:
-----------------------------------------------------------------
I reviewed a similar patch as part of Bug 813683, I guess this is not the right attachment for this bug.
Attachment #8793121 -
Flags: review?(nicolas.b.pierron)
| Assignee | ||
Comment 6•9 years ago
|
||
Yeah, wow, I totally crossed the two bugs I was working on yesterday. :-(
Flags: needinfo?(terrence.d.cole)
| Assignee | ||
Comment 7•9 years ago
|
||
I did not mean to overwrite the original patch in this bug.
Attachment #8793121 -
Attachment is obsolete: true
Attachment #8793373 -
Flags: review?(jcoppeard)
Comment 8•9 years ago
|
||
Comment on attachment 8793373 [details] [diff] [review]
fix_pre_compacting_interrupt-v0.diff
Review of attachment 8793373 [details] [diff] [review]:
-----------------------------------------------------------------
Yeah this looks good.
Attachment #8793373 -
Flags: review?(jcoppeard) → review+
Pushed by tcole@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/755e16dfd05a
Fix the pre-compacting interrupt's position; r=jonco
Comment 10•9 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox52:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Comment 11•9 years ago
|
||
| bugherder | ||
Updated•9 years ago
|
Keywords: regression
Comment 12•9 years ago
|
||
Hi :jonco,
Since this bug is a regression and also affects 51, do you consider to uplift this for 51 if this patch is not too risky?
Flags: needinfo?(jcoppeard)
Comment 13•9 years ago
|
||
Comment on attachment 8793373 [details] [diff] [review]
fix_pre_compacting_interrupt-v0.diff
Approval Request Comment
[Feature/regressing bug #]: Bug 1249367
[User impact if declined]: Possible jank due to garbage collection.
[Describe test coverage new/current, TreeHerder]: On m-c since 23rd September.
[Risks and why]: Low.
[String/UUID change made/needed]: None.
Flags: needinfo?(jcoppeard)
Attachment #8793373 -
Flags: approval-mozilla-aurora?
Comment 14•9 years ago
|
||
Comment on attachment 8793373 [details] [diff] [review]
fix_pre_compacting_interrupt-v0.diff
Fix a regression related to GC. Take it in 51 aurora.
Attachment #8793373 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 15•9 years ago
|
||
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•