Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×
Firefox

Submission + - Firefox javascript engine becomes single threaded (mozilla.com)

An anonymous reader writes: From Mozilla engineer Luke Wagner's Blog:
With web workers in separate runtimes, there were no significant multi-threaded runtime uses remaining. Furthermore, to achieve single-threaded compartments, the platform features that allowed JS to easily ship a closure off to another thread had been removed since closures fundamentally carry with them a reference to their original enclosing scope. Even non-Mozilla SpiderMonkey embeddings had reportedly experienced problems that pushed them toward a similar shared-nothing design. Thus, there was little reason to maintain the non-trivial complexity caused by multi-threading support.

There are a lot of things that “would be nice” but what pushed us over the edge is that a single-threaded runtime allows us to hoist a lot data currently stored per-compartment into the runtime. This provides immediate memory savings.

This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Firefox javascript engine becomes single threaded

Comments Filter:

Once it hits the fan, the only rational choice is to sweep it up, package it, and sell it as fertilizer.

Working...