On Feb 13, 5:25 pm, Benjamin Smedberg <[email protected]> wrote: > On 2/13/2013 4:28 PM, Kyle Huey wrote: > > > > > > > > > On Wed, Feb 13, 2013 at 9:20 PM, Benjamin Smedberg > > <[email protected]>wrote: > > >> On 2/13/2013 1:39 PM, Kyle Huey wrote: > > >>> On Wed, Feb 13, 2013 at 6:35 PM, Brian Smith <[email protected]> wrote: > > >>> At what point during XPCOM shutdown are workers destroyed? > >>>> xpcom-shutdown-threads > >> What workers are these? Do workers outlast the page that loaded them? The > >> entire DOM should be torn down at or before we shut down the profile. > >> There's really no way workers should outlive that point either. > > > Web workers for a given window begin to shut down when > > nsGlobalWindow::FreeInnerObjects is called. When exiting that's going to > > get called from nsDocShell::Destroy, presumably when the <tabbrowser> is > > torn down. Since workers are on another thread the shutdown process is > > asynchronous. Nothing guarantees that they are shutdown before proceeding > > further until we block on them being shutdown during xpcom-shutdown-threads. > > Yes, but the immediately are unable to send messages back, right? So > what could they *do* that would affect anything else? > > --BDS
Don't workers have access to XMLHttpRequest? _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
