Closed
Bug 734946
Opened 13 years ago
Closed 13 years ago
Disable incremental GC for Firefox 13
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
VERIFIED
FIXED
mozilla13
People
(Reporter: billm, Assigned: billm)
Details
(Whiteboard: [qa!])
Attachments
(1 file)
(deleted),
patch
|
dmandelin
:
review+
|
Details | Diff | Splinter Review |
I haven't made much progress in fixing the leaks related to bug 728686, and I think it's a bad idea to ship in the state we're in (where incremental GC gets randomly disabled). I think it would be better to disable incremental GC by default and then land the patch for bug 728686. That way, people who choose to opt in to incremental GC will have it on all the time.
Attachment #605013 -
Flags: review?(dmandelin)
Updated•13 years ago
|
Attachment #605013 -
Flags: review?(dmandelin) → review+
Comment 1•13 years ago
|
||
Do you think it would be useful to provide a tiny Jetpack add-on to enable IGC?
Assignee | ||
Comment 2•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/8cae4bde9534
(In reply to David Mandelin from comment #1)
> Do you think it would be useful to provide a tiny Jetpack add-on to enable
> IGC?
I don't know. about:config doesn't seem like much of a barrier to entry to me.
Assignee | ||
Updated•13 years ago
|
Target Milestone: --- → mozilla13
Assignee | ||
Comment 3•13 years ago
|
||
Blargh. Tryserver shows *this* patch to be leaking. Has the world gone mad?
https://hg.mozilla.org/integration/mozilla-inbound/rev/6799a5e6912f
Target Milestone: mozilla13 → ---
Comment 4•13 years ago
|
||
If we're in a situation in which our tests are telling us that incremental GC is required in order to stop Firefox from leaking, that's bad. I would think that this has to be fixed on Aurora before Firefox 13 can be released.
Since it looks like IGC is going to get uplifted (as I assume uplifts can't happen unless our trees are green), could we just land IGC leak fixes on Aurora?
Comment 6•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
Comment 7•13 years ago
|
||
Actually, looks like Bill backed this out.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla13 → ---
Assignee | ||
Comment 8•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a625b9ed671f
Relanded. Looks like the leaks were "fixed" in bug 734554. This sort of thing makes me hate Firefox.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Target Milestone: --- → mozilla13
Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120313 Firefox/13.0a1
about:config shows javascript.options.mem.gc_incremental;false yet about:support shows:
JavaScript
Incremental GC: 1
Is that a bug?
Assignee | ||
Comment 10•13 years ago
|
||
(In reply to Daniel Cater from comment #9)
> Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120313 Firefox/13.0a1
>
> about:config shows javascript.options.mem.gc_incremental;false yet
> about:support shows:
>
> JavaScript
> Incremental GC: 1
>
> Is that a bug?
It's not a bug, although it's admittedly confusing. The about:support line is only showing whether incremental GC is permanently disabled due to binary add-ons. Incremental GC may also be disabled for other reasons (like the preference being off).
Comment 11•13 years ago
|
||
Verified as fixed on:
Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120318 Firefox/13.0a2
Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120319 Firefox/13.0a2
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120318 Firefox/13.0a2
Status: RESOLVED → VERIFIED
Whiteboard: [qa!]
You need to log in
before you can comment on or make changes to this bug.
Description
•