Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Debugger statement stops firefox to a crawl after reloading webapp

  • 1 réponse
  • 1 a ce problème
  • 1 vue
  • Dernière réponse par Svetlana

erzei
erzei
more options

I'm testing several webapps on Firefox 58 and the problem is that when I insert the debugger statement on my javascript code(react 16+) and the app hot reloads itself, the first time the debugger tab of the developer tools shows all the info I need and the current state of my app.

But, If I modify something else and reload my app or just refresh the current page, with the debugger statement still on the code, the browser slows down until the UI of the entire browser is unresponsive to my mouse clicks and the debugger tab shows nothing at all.

The only way to be able to exit this state is to close the developer tools, where the browser exits its frozen status and all the tabs and the UI start to function again.

This was happening in firefox 57, also I've tested the same code on Chrome and none of the freezing occurs.

I'm testing several webapps on Firefox 58 and the problem is that when I insert the debugger statement on my javascript code(react 16+) and the app hot reloads itself, the first time the debugger tab of the developer tools shows all the info I need and the current state of my app. But, If I modify something else and reload my app or just refresh the current page, with the debugger statement still on the code, the browser slows down until the UI of the entire browser is unresponsive to my mouse clicks and the debugger tab shows nothing at all. The only way to be able to exit this state is to close the developer tools, where the browser exits its frozen status and all the tabs and the UI start to function again. This was happening in firefox 57, also I've tested the same code on Chrome and none of the freezing occurs.

Modifié le par erzei

Toutes les réponses (1)

Svetlana
Svetlana
more options

1. Do you have a small hello world app that reproduces this problem? Please provide a copy. This may help me reproduce the issue.

2. Please test for this issue in Firefox's Safe Mode. It opens a Firefox session without your customization temporarily, which may help to identify the problem.