Thanks for the heads up. I’m tracking the bug too, just in case it requires a change to the docs.
Chris Mills Senior tech writer || Mozilla developer.mozilla.org || MDN [email protected] || @chrisdavidmills > On 23 Sep 2015, at 02:37, Ting-Yu Chou <[email protected]> wrote: > > Should be bug 1204837, which now Nuwa never gets ready. > > Ting > > On Wed, Sep 23, 2015 at 1:46 AM, Sam Foster <[email protected]> wrote: > The mdn page > https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Boot_to_Gecko_%28with_a_real_device%29 > says I should be able to use the "Preallocated" pid to profile app startup - > i.e. the app is not running yet so I don't know its pid to include in my > ./profile.sh start params. > > But when I check ./profile.sh ps (or b2g-ps) I only see this list: > > PID Name > ----- ---------------- > 4384 b2g profiler not running > 4397 (Nuwa) profiler not running > 4600 Default Home Sc profiler not running > 4621 Built-in Keyboa profiler not running > > Did something change, is there another to way do this now? > > /Sam > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
