question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Loading in profiles for development section of Contributing to the Firefox Profiler guide is confusing.

See original GitHub issue

I am reading through the Contributing to the Firefox Profiler guide while trying to set up the project locally. loading in profiles for development section briefly confused me because the introductry statement says:

The web app doesn’t include any performance profiles by default, so you’ll need to load some in. Make sure the local Webpack web server is running, and then try one of the following:

Being a newbie, my first interpretation of “and then try one of the following” closing statement was to try one of the steps mentioned in the first three bullet points i.e. one of:

  • Use an existing profile from the web: replace the https://profiler.firefox.com with http://localhost:4242 (be careful: the leading https changes to http!).
  • Drag in a saved profile to the loading screen (this makes refreshing hard).
  • Record a new profile.

instead of trying the steps outlined in the first set of bullet points or the second set of bullet points.

It think it would be less confusing if the statement was modified to “Make sure the local Webpack web server is running, and then try either Method 1 or Method 2”. Then the two methods can be modified to:

Method 1

  1. Use an existing profile from the web: replace the https://profiler.firefox.com with http://localhost:4242 (be careful: the leading https changes to http!).
  2. Drag in a saved profile to the loading screen (this makes refreshing hard).
  3. Record a new profile.

Method 2

  1. Open about:config in Firefox.
  2. Change devtools.performance.recording.ui-base-url to http://localhost:4242 or to the localhost with the proper port you have configured.
  3. Ensure the profiler menu button is active by clicking the button on the profiler.firefox.com homepage to enable it.
  4. Record a profile using the menu button, and it should open up in your local environment.

Instead of Method 1 and Method 2, a meaningful name can be used.

I think it will help other beginners following through the set-up instructions from getting confused like me.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
Somaru-chancommented, Oct 17, 2020

Following the advice kindly provided by @mstange, I’ve edited a few things emphasized in italic:

“…and then try one of the following methods:” 1- Record a profile: if you are setting up your environment for the first time. 2- Use an existing profile: using a profile that’s been shared with you.

1- Record a profile:

  • Open about:config in Firefox.
  • Change devtools.performance.recording.ui-base-url to http://localhost:4242. Or to the localhost with the proper port you have configured.
  • Ensure the profiler menu button is active by clicking the button on the profiler.firefox.com homepage to enable it.
  • Record a profile using the menu button, and it should open up in your local environment.

2- Use an existing profile:

  • On the web, replace the https://profiler.firefox.com with your existing profile URL.
  • Alternatively, if a profile has been previously downloaded, drag and drop it to the loading screen (this may hinder refreshing).

How does this sound?

1reaction
Somaru-chancommented, Oct 15, 2020

How about:

“…and then try one of the following methods:” 1- Record a profile: if you are setting up your environment for the first time. 2- Use an existing profile from the web: using a profile that’s been shared with you.

1- Record a profile:

  • Open about:config in Firefox.
  • Change devtools.performance.recording.ui-base-url to http://localhost:4242 or to the localhost with the proper port you have configured.
  • Ensure the profiler menu button is active by clicking the button on the profiler.firefox.com homepage to enable it.
  • Record a profile using the menu button, and it should open up in your local environment.

2- Use an existing profile from the web:


I’m not sure if the brief description of “Record a profile” is sufficient or requires editing. Any feedback is welcome 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

profiler/CONTRIBUTING.md at main · firefox-devtools ... - GitHub
Getting started with development. profiler.firefox.com is a web application that loads in performance profiles for analysis. The profiles are loaded in from ...
Read more >
Performance Tool in Firefox DevTools Reloaded - Mozilla Hacks
This panel is now based on the Firefox profiler tool that can be used to capture a performance profile for a web page,...
Read more >
Profiling with the Firefox Profiler
Reporting a Performance Problem has a step-by-step guide for obtaining a profile when requested by Firefox developers. Interface. 1. Timeline. The timeline has ......
Read more >
Profiling with the built-in profiler - Mozilla | MDN
Profiling local Windows builds; Profiling Firefox mobile ... profiler that can be opened from the menu Tools > Web Developer > Performance.
Read more >
ISE Profiling Design Guide - Cisco Community
This section reviews the steps to enable the various ISE probes to collect different endpoint attributes. Working configuration examples of supporting network ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found