Closed
Bug 729367
Opened 12 years ago
Closed 12 years ago
Add additional JSCLASS_IMPLEMENTS_BARRIERS flags
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla13
People
(Reporter: billm, Assigned: billm)
Details
Attachments
(2 files)
3.61 KB,
patch
|
jorendorff
:
review+
|
Details | Diff | Splinter Review |
990 bytes,
patch
|
igor
:
review+
|
Details | Diff | Splinter Review |
We're still disabling write barriers in cases where we shouldn't.
Assignee | ||
Comment 1•12 years ago
|
||
Shell workers don't have the JSCLASS_IMPLEMENTS_BARRIERS, but that's because they don't implement write barriers. However, if we leave off the flag, then incremental GC will be disabled when we initialize workers at shell startup. I hacked around this by putting the flag on, but immediately disabling incremental GC if workers are ever used.
Attachment #599418 -
Flags: review?(jorendorff)
Assignee | ||
Comment 2•12 years ago
|
||
I also forgot to put the flag on some NPAPI code. I audited this code a while ago, and it didn't need any barriers.
Attachment #599419 -
Flags: review?(igor)
Updated•12 years ago
|
Attachment #599419 -
Flags: review?(igor) → review+
Updated•12 years ago
|
Attachment #599418 -
Flags: review?(jorendorff) → review+
Assignee | ||
Comment 3•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/05af8fc6c379 https://hg.mozilla.org/integration/mozilla-inbound/rev/1a49c1500abd
Target Milestone: --- → mozilla13
Comment 4•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/1a49c1500abd https://hg.mozilla.org/mozilla-central/rev/05af8fc6c379
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•