Hi Manjunatha, https://wiki.mozilla.org/B2G/Architecture provides an overview of the various processes.
The content apps run with very low priviledge levels and commuicate with the main process via IPC (over pipes). Each content app has a main thread and various other threads. JS mostly runs on the main thread, although I think that there are web workers that run on their own threads. The gecko/gonk layer create helper threads whenever it makes sense. We often use https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler for performance profiling. Some links about memory reporting/profiling https://wiki.mozilla.org/B2G/Debugging_OOMs http://blog.mozilla.org/nnethercote/category/b2g/ Dave Hylands ----- Original Message ----- > From: "Manjunatha M" <[email protected]> > To: [email protected] > Sent: Wednesday, November 13, 2013 5:39:18 AM > Subject: [b2g] Process Architecture. > > Hi All, > > I want to understand how each app runs as a process in Firefox though the > system application creates a new iFrame to launch the web application. > (Basically the process model) > > > How the thread splits happens at each layer Gaia , Gecko, Gonk? > > Can you share links with respect to the memory management and memory > profiling? > > -- > Regards, > Manjunatha > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
