Please create an account to participate in the Slashdot moderation system


Forgot your password?

Submission Firefox javascript engine becomes single threaded->

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.

Link to Original Source
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:

In space, no one can hear you fart.