Brendan Eich wrote: > Benjamin Smedberg wrote: >> Brendan may kill me for this, but I think that we can and should assert >> single-threaded behavior for all of JS and "XPCOM/MMGC": that is, MMGC >> should only be on the main thread. > > Jason addressed the request model fear. Main thread code can't block > indefinitely for i/o already, so the only request suspend points that I > can see right now are > > * lengthy, non-GC-graph-mutating computations;
These are UI starvation bugs to fix already, btw. > * file i/o that's "blocking, but fast", yet not fast enough for us to > wish to stay in a request; I'm thinking of local file i/o, but we do that non-blocking too, don't we? > * required deadlock-with-the-GC avoidance not handled by the request > model itself. This would be something like the cycle collector, for Java and C-Python if we care to avoid cross-heap leaks with those runtimes. /be _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
