We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 2 respostas
  • 1 tem este problema
  • 1 exibição
  • Última resposta de 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.

Alterado por idbentley em

Todas as respostas (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