Now that Nuwa is enabled on master and 1.3, if you try to get a memory
report using $B2G/tools/get_about_memory.py you'll notice that the
process is stuck mid-way. That's because the nuwa process is frozen and
doesn't answer to the request for a memory dump.
While we'd still like to know how the nuwa process is using its memory,
doing it properly is quite involved. In the meantime khuey landed a
change to get_about_memory.py: you need to set the
MOZ_IGNORE_NUWA_PROCESS environment variable to 1 if you profile a build
with nuwa enabled.
This is part of gonk-misc, so you need to update your main B2G repo.
Happy memory profiling!
Fabrice
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
