GC: missing barriers on script atoms

RESOLVED FIXED in mozilla14

Status

()

Core
JavaScript Engine
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: terrence, Assigned: terrence)

Tracking

Trunk
mozilla14
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 612721 [details] [diff] [review]
v0

These are only inited and read from, but we need to barrier the init correctly in-case any of the atoms reside in the nursery.
Attachment #612721 - Flags: review?(wmccloskey)
Comment on attachment 612721 [details] [diff] [review]
v0

As Luke would say, righteous.

If it's not too much trouble, could you move js_InitAtomMap into the js namespace?
Attachment #612721 - Flags: review?(wmccloskey) → review+
(Assignee)

Comment 2

5 years ago
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=a72502cf4dac
https://hg.mozilla.org/mozilla-central/rev/a72502cf4dac
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
You need to log in before you can comment on or make changes to this bug.