I guess the question is how do you define "after we've entered shutdown".
For the preallocated process manager both "profile-change-teardown" and "xpcom-shutdown" will prevent any further process spawning. For the preloaded browser in tabbrowser.xml we usually instead of creating a process for the hidden about:blank page we select an existing one, however if there is non around (the browser has only some chrome pages open when the shutdown is initiated) then it can create a process and I'm not sure if anything would prevent the process creation now that I'm thinking about it. I think we should set some flag when some of these shutdown related notifications are fired and based on that prevent any new content process creation somewhere in ContentParent::LaunchSubprocess. Since I don't see any legit use case for it and I'm pretty sure it usually ends up with crashes or hangs. Gabor On Wed, Sep 20, 2017 at 8:38 PM, Milan Sreckovic <msrecko...@mozilla.com> wrote: > I've spoken to some of you about this, but at this point need a larger > audience to make sure we're covering all the bases. > > Do we have code in Firefox that would cause us to create a new content > process, after we've entered shutdown? > > I understand the possibility of user action that would create a new > content process followed quickly by one that would cause shutdown, and the > timing making it so that the new content process initialization can then > happen out of order, but I'm more asking about the explicit scenario. > > Thanks! > > -- > - Milan (mi...@mozilla.com) > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
