Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox takes a very long time to load sourceMaps, and doesn't improve during subsequent refreshes

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

more options

Confirmed on this device (Firefox 33.0 on Linux) and with Firefox 33.0 on Mac OS X Maverics.

Without developer tools open, my site loads in <1s. When developer tools are opened, and I navigate to the debug tab for the first time, the browser consumes 100% of one of my cores for ~60s. It eventually completes the processing (sometimes firefox reports a slow script, but if it is allowed to run, it finishes), and performs normally - sourceMaps seem to work fine. On each subsequent page load, the browser behaves as when navigating to the debug tab for the first time.

Cursory testing in a recent version of Chromium does not have the same slowness.

The site contains a fairly large amount of javacript, which is processed by browserify as part of our build process. Browserify is responsible for generating the sourceMaps.

Confirmed on this device (Firefox 33.0 on Linux) and with Firefox 33.0 on Mac OS X Maverics. Without developer tools open, my site loads in <1s. When developer tools are opened, and I navigate to the debug tab for the first time, the browser consumes 100% of one of my cores for ~60s. It eventually completes the processing (sometimes firefox reports a slow script, but if it is allowed to run, it finishes), and performs normally - sourceMaps seem to work fine. On each subsequent page load, the browser behaves as when navigating to the debug tab for the first time. Cursory testing in a recent version of Chromium does not have the same slowness. The site contains a fairly large amount of javacript, which is processed by browserify as part of our build process. Browserify is responsible for generating the sourceMaps.

Modified by idbentley

All Replies (2)

more options
more options

You could try to disable this feature for now by toggling this pref on the about:config page:

  • devtools.debugger.source-maps-enabled = false