Profiled the CrystalSkull app on B2G (otoro), following the instructions there: https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler I added STRIP_FLAGS="--strip-debug" to the default-gecko-config as suggested there. Resulting profile: http://people.mozilla.com/~bgirard/cleopatra/?report=2eefe20c6df6753ff3f06d5f2f200342922eaff6 What's really puzzling is that filtering for WebGL and for GLContext doesn't give any result. The profile starts with 81% time spent in ProcessNextNativeEvent::Wait. Does this make sense? Does it mean we're idling 81% of the time? Then there is some Layout work, with some display list work. And some JS work. But no WebGL, and the only gfx stuff seems unrelated to WebGL (some thebes-layer stuff, likely for the digital clock at the top of the screen (?) ). The other weird thing is the built-in FPS counter. It claims 20 FPS, but clearly we're not getting 20 FPS, more like 10 FPS. Some WebGL frames must be getting composited twice.

Crystalskull runa in its own procesa. We overcompoaitw at the moment, mattwoodrow has patches to fix about to land. phone

(In reply to Chris Jones [:cjones] [:warhammer] from comment #1) > Crystalskull runa in its own procesa. Pardon me, my Swedish is a bit rusty. > We overcompoaitw at the moment, My Gaelic too! > mattwoodrow has patches to fix about to land. Cool! I'll retry with those patches. For the "own process" part, I suppose I just have to follow the profiling instructions for content processes.

Matt, what's the bug # for overcompositing on B2G?

Firefox OS is not being worked on