Changes

== Using Cleopatra Profiler Devtools ==* 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.

* Follow all For <strong>remote profiling</strong>, follow the steps here revolving around prefs/settings and read {{bug|886555}} on getting the set profiler going. * Before you start** You must have metro installed & working** You must access 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 instructions above those rules if you get lost or stuck.** If you are on wifi, both devices must be on the same network to get 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 prefs set right hardware for dev tools it. * Setup** Go to about:config on classic/ desktop fx*** devtools.debugger.force-local -> false*** devtools.debugger.remote-enabled -> true*** Check that these values are what you want**** devtools.debugger.remote debugging-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.debugger.log -> true**** browser.dom.window.dump.enabled -> true** Restart classic/desktop fx*** You need to restart for the next step to work.* Install * Navigate Firefox button -> Web Developer -> "Connect.." entry between the profiler extension from: Error Console" & "Get More Tools" Entry*** https://githubdeveloper.mozilla.comorg/en-US/bgirarddocs/Gecko-Profiler-AddonMozilla/rawFirefox_OS/masterDebugging/geckoprofilerSetting_up is what this step is based on** Go to about:config on metrofx*** devtools.debugger.xpiforce-local -> false*** devtools.debugger.remote-enabled -> true*** 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 set fx, click the pref 'profiler"Connect...threads' " 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 and the port number if you'profilerve changed them.stackwalk*** If you are connecting on a localhost, you shouldn' t need to truechange the default settings.* Restart* From Click the toolbar connect button dropdown, select TCP, enter in classic fx** On metrofx a strap(the metro browser's ip addressversion of the modal dialog) will appear about an incoming connection.*** Click/tap "allow"** On classic fx, and click the connectpage will reload with a list of active tabs & processes. You should get a remote connection warning in Usually 'main process' is the metro browsermost interesting.* After you have finishes collecting data* The devtools console will appear & the aforementioned tab on classic fx will disappear** Sally forth & debug! * Notes** I usually pair on localhost, click analyzeusing an external monitor so I can see metrofx & classicfx at the same time.* Wait * If you are using localhost without an external monitor, beware of windows suspending the metrofx while its waiting for the profile view incoming connection. This will cause the pairing to load (this may take fail.** While you can pair classic/metrofx running out of the same obj dir, I frequently experienced unexpected hangs and crashes as a while!)result.* For additional detail read {{bug|886555}} on getting things going.* if you close the devtools window, this usually results in the metro browser shutting down