Jason Orendorff wrote: > * Add thread-safety to MMgc using the Spidermonkey request model.
We currently don't pay the cost of thread-safety for most XPCOM objects, since most objects are main-thread-only. Would doing this impose significant performance penalties for locking or atomic operations? Or would most operations still be cheap? > * Delete the cycle collector. Are we dropping the multi-language aspects of the platform (introduced in this milestone, at considerable effort in https://bugzilla.mozilla.org/show_bug.cgi?id=255942 )? Or is there a good way for python to use MMgc as well? (That said, the python stuff hasn't caught up with the cycle collector, and would probably leak a lot if it were used as intensively as we use JS, so I'm not sure how seriously we should take it.) -David -- L. David Baron http://dbaron.org/ Mozilla Corporation http://www.mozilla.com/ _______________________________________________ dev-tech-xpcom mailing list dev-tech-xpcom@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-xpcom
