Changes

== Using Devtools Cleopatra Profiler ==* Tracking bug https://bugzilla.mozilla.org/show_bug.cgi?id=850019** There are known issues with the profiler. All other parts should be functional, modulo the refactoring work the devtools team is doing on them.* This hooks into the tools developed & maintained by the devtools team.* They have been refactoring & improving their tools, so it <strong>highly encouraged</strong> to use Nightly builds on both sides of the pairing if possible.

* For <strong>remote profiling</strong>, follow Follow all the steps here revolving around prefs/settings and read {{bug|886555}} on getting the profiler going. * Before you start** You must have metro installed & working** You must access set up instructions above to a classic/desktop fx. This need not be a local build** If you are connecting remotely, you must make sure both machines can ping each other before starting. This will save you a lot of grief later*** on windows ipconfig in the cmdline is helpful in getting your ip address*** on windows 8 this usually means disabling the firewall (not encouraged) or adding inbound/outbound firewall rules to allow them to connect.**** If you need it, Peter in IT now knows a fair bit about setting up those rules if you get lost or stuck.** If you are on wifi, both devices must be on the same network to communicate. Mozilla != Mozilla-G. *** It sounds silly but some of the windows devices only see Mozilla-G and the older company issued thinkpads do not have the hardware prefs set right for it. * Setup** Go to about:config on classicdev tools /desktop fx*** devtools.debugger.force-local -> false*** devtools.debugger.remote-enabled -> true*** Check that these values are what you want**** devtools.debugger.remote-port -> 6000 (I'd leave this one alone unless you have a compelling reason to change it)*** If you don't have these, you'll probably want these as well**** devtools.debuggerdebugging.log -> true**** browser.dom.window.dump.enabled -> true** Restart classic/desktop fx*** You need to restart for Install the next step to work.** Navigate Firefox button -> Web Developer -> "Connect.." entry between the Error Console" & "Get More Tools" Entry*** profiler extension from: https://developergithub.mozilla.orgcom/bgirard/enGecko-USProfiler-Addon/docsraw/Mozillamaster/Firefox_OS/Debugging/Setting_up is what this step is based on** Go to about:config on metrofx*** devtools.debuggergeckoprofiler.force-local -> false*** devtools.debugger.remote-enabled -> truexpi*** and you may want**** devtools.debugger.log -> true**** devtools.errorconsole.enabled -> true**** browser.dom.window.dump.enabled -> true*** devtools.debugger.remote-port -> 6000 (again I'd leave this one alone)*** It is unclear if a restart is required. I frequently do in the test-build-dev cycle anyway.** Make sure metrofx is started (and not suspended)** In classic fx, click set the "Connectpref 'profiler..." entry *** Depending on your version, this will launch a new tab or a new panel on firefox*** Enter the ip of metrofx if you are connecting remotely threads' and the port number if you've changed themprofiler.*** If you are connecting on a localhost, you shouldnstackwalk't need to change the default settingstrue.*Restart* Click From the connect toolbar button in classic fx** On metrofx a strap(dropdown, select TCP, enter the metro version of the modal dialog) will appear about an incoming connection.*** Click/tap "allow"** On classic fxbrowser's ip address, the and click connect page will reload with . You should get a list of active tabs & processes. Usually 'main process' is remote connection warning in the most interestingmetro browser.** The devtools console will appear & the aforementioned tab on classic fx will disappear** Sally forth & debug! * Notes** I usually pair on localhostAfter you have finishes collecting data, using an external monitor so I can see metrofx & classicfx at the same timeclick analyze.** If you are using localhost without an external monitor, beware of windows suspending the metrofx while its waiting Wait for the incoming connection. This will cause the pairing profile view to fail.load (this may take a while!)** While you can pair classic/metrofx running out of the same obj dir, I frequently experienced unexpected hangs and crashes as a resultFor additional detail read {{bug|886555}} on getting things going.** if you close the devtools window, this usually results in the metro browser shutting down