On Thu, Apr 18, 2013 at 2:48 AM, Justin Lebar <[email protected]> wrote: > It's possible that the main process is taking CPU time from the child > process, and that's why it appears that the child process's event loop > is busy at that point in time. But if you want to know the answer for > sure, you'd have to profile. We have tools that will let you get a > fairly complete picture of what's going on.
I tried a b2g build with the 1ms profile patch applied and did a profile.sh capture. It did not seem to account for all the time, but I am very new to deciphering the output. I wrote up what I could make out of it and opened a ticket that points to the perf capture, as it seems like that may be a more appropriate channel for this kind of thing: https://bugzilla.mozilla.org/show_bug.cgi?id=863870 James _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
