On 10/23/17 10:30 AM, Jeff Muizelaar wrote:
For the curious among us, what made nsIURI not thread safe in the first place?
There were several aspects to this:
1) Constructing a URI object. This needed a protocol handler, which
could be implemented in JS by extensions. With XPCOM extensions gone,
we probably still need to audit our protocol handlers to ensure they're
threadsafe.
2) Necko caches the protocol handler for a scheme after the first time
you get it. This cache is obviously shared mutable global state, and is
not threadsafe at the moment.
3) The URI could be implemented in JS by extensions. Again, with that
gone we need to audit our built-in URI implementations to ensure they're
threadsafe. Some of this work (and fixing the threadsafety issues it
uncovered) happened in
https://bugzilla.mozilla.org/show_bug.cgi?id=1344751 already.
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
