Closed Bug 984684 Opened 10 years ago Closed 10 years ago

Do not fire post barriers on shared atoms from workers

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla31

People

(Reporter: terrence, Assigned: terrence)

References

Details

Attachments

(1 file)

We are currently falling on many tests on maple because we are hitting an assertion: CurrentThreadOwnsRuntime(cell->runtime()). It turns out these |cell| are all coming from shared atoms. This patch copies the test we are currently doing for pre-barriers to the JS::Heap post-barrier.

This is potentially an issue for the in-engine barriers too as they also see shared atoms. They do not, however, have workers that implement barriers, so this doesn't matter. If we do ever have invalid off-thread usage at some point, the same assertions will catch that usage; for now I'm just going to leave our in-engine barriers alone.
Attachment #8392577 - Flags: review?(bhackett1024)
Attachment #8392577 - Flags: review?(bhackett1024) → review+
https://hg.mozilla.org/mozilla-central/rev/405082f9ce44
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
I am dumb and only fixed case that was hit. We also need the non-relocate case.

https://hg.mozilla.org/integration/mozilla-inbound/rev/e5c54354e723
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://hg.mozilla.org/mozilla-central/rev/e5c54354e723
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: