Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Debugger statement stops firefox to a crawl after reloading webapp

  • 1 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: Svetlana

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.

글쓴이 erzei 수정일시

모든 댓글 (1)

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.