Mike Shaver wrote: > Other than that, and the case where we actually construct a component > _loader_ on two threads at the same time -- a lock there wouldn't kill > us, if we could restrict it to the creation case, the only other > possible races are component registration racing with creation and > scraping its knee on dhash growth and reallocation. Not sure it's worth > fixing that the "easy" way, because it will reintroduce pervasive > locking costs to the CI path, when we should probably rendezvous with > all non-main threads via the XPCOM thread event queue and proxy all > registrations to the main thread. Component registration is extremely > rare, and we want to push all costs to that uncommon path.
Hrm, we may also need to worry about managing the locking of the factory hashtable. That will be much more problematic. Mike
