Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to threadsafe builds. #92

Merged
merged 3 commits into from Jul 24, 2014
Merged

Switch to threadsafe builds. #92

merged 3 commits into from Jul 24, 2014

Conversation

@Ms2ger
Copy link
Collaborator

Ms2ger commented Jul 24, 2014

No description provided.

Ms2ger added 3 commits Jul 22, 2014
In order to support threadsafe builds (which are necessary for thread-safety
assertions and which will become the only available configuration in future
versions), we need to link to NSPR for threading primitives.
In threadsafe builds, we should enter a request whenever we call into
SpiderMonkey. The JSAutoRequest class makes that simpler.
Consumers should be using native rather than green tasks, to avoid calling
into the same JSRuntime from multiple OS threads.

For native tasks, SpiderMonkey can figure out the correct stack bounds for
itself. Rust, on the other hand, apparently cannot; the existing code leads to
crashes during conservative stack marking.
jdm added a commit that referenced this pull request Jul 24, 2014
Switch to threadsafe builds.
@jdm jdm merged commit 6bb7ae1 into servo:master Jul 24, 2014
Ms2ger added a commit that referenced this pull request Aug 3, 2014
The Servo changes to move the script task to a native task are not progressing
as fast as hoped, so these changes should be temporarily reverted.
Ms2ger added a commit that referenced this pull request Aug 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.