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!

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Debugger statement stops firefox to a crawl after reloading webapp

  • 1 wótegrono
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót 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.

Wót erzei změnjony

Wšykne wótegrona (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.