[Mobile Profiling] Spec
We should be able to profile Firefox on mobile. This involves making sure that the new DevTools panel works correctly when profiling remotely. I didn't test it specifically for this use case. We should also have support documentation on how to do this, and actually talk to some engineers working on that side of things to make sure we are supporting them properly.
I'm not sure what symbolication looks like, but perhaps we have some things that need to be done to properly symbolicate. mstange do you know what we need?
In summary, the concrete steps are:
- [ ] Talk to mobile Firefox engineers.
- [ ] Test and update the Firefox DevTools new performance to make sure it supports this workflow correctly.
- [ ] Write end-user documentation.
- [ ] Support symbolication.
┆Issue is synchronized with this Jira Task
From https://github.com/devtools-html/Gecko-Profiler-Addon/issues/35 per @mstange:
I think we should address symbolication in three tiers:
- Symbolicate Gecko libraries, official builds only. This should only require bug 1350500 and then we should automatically find the right symbol dump on symbols.mozilla.org.
- Symbolicate Gecko libraries from local builds. For this we need to know where the objdir on the developer's machine is, and run dump_syms or nm on the binaries in the objdir. (For nm we need to know where the NDK tools are.)
- Symbolicate system libraries from the phone. For this we need to know the absolute paths of those libs (bug 1350501), and we need to be able to pull them to the Desktop machine usind adb (so we need to know where adb is).
@gregtatum is there anything left to do from what was described here?